Attackers Exploit Critical Sangoma Switchvox SQL Injection Flaw CVE-2026-9586 to Deploy Reverse Shells Without Credentials
Administrators of VoIP systems and IT security teams face an urgent new threat: a critical vulnerability in Sangoma Switchvox that enables remote code execution without any credentials. The flaw, identified as CVE-2026-9586 and rated CVSS 9.3, has already been exploited in real-world attacks to deploy reverse shells since August 30, 2026.
The vulnerability resides in the HTTP endpoint /pa, which processes XML requests. The system inserts the PhoneIP value directly into PostgreSQL queries without proper sanitization or parameterization. This classic CWE-89 SQL injection pattern allows attackers to run arbitrary database commands and escalate to full system command execution with PostgreSQL superuser privileges.
Observed attack activity includes the immediate opening of reverse shells and basic reconnaissance. Attackers use Base64-encoded commands to enumerate running processes and map the compromised server environment. One IP address linked to the campaign is 176.65.148.184. Forensic traces may appear in the log file /var/log/switchvox/db-quirks.log, which records attempted SQL injections and subsequent actions.
Patch Availability and Timeline
Sangoma released the corrective update in Switchvox 8.4.0.2 on July 14, 2026. The patch addresses the injection flaw along with additional web portal fixes. The disclosure timeline shows the initial report to the vendor on April 10, 2026, the patch release in mid-July, and confirmed exploitation by late August.
Thousands of Switchvox instances remain reachable from the internet, with a notable concentration in the United States. Organizations should prioritize immediate upgrades to version 8.4.0.2 or later, especially for any deployments exposed to untrusted networks.
Recommended Mitigations and Detection
- Apply the Switchvox 8.4.0.2 update without delay.
- Restrict access to the HTTP service using network segmentation, VPNs, or access control lists until patching is complete.
- Monitor outbound connections for anomalies, particularly attempts to reach 176.65.148.184 or the use of tools such as nc and unexpected bash invocations from web services.
- Inspect logs for signs of post-exploitation and rotate all associated credentials if compromise is suspected.
Additional technical details are available from The Hacker News and Horizon3.ai research reports, as well as official Sangoma release notes.
Related articles
Gmail Address Variants Bypass String Comparison and Enable Multiple Registrations
A single user created four separate accounts using valid Gmail address formats that all deliver to the same inbox: Ivan.Petrov@gmail.com, ivanpetrov@gmail.com, ivan.petrov+shop@gmail.com, and IVAN.PETROV@gmail.com. Simple string comparison in the registration code treated these as distinct entries, allowing circumvention of new-user promotions, free-tier limits, and one-application-per-person rules. The root cause lies in three Gmail-specific behaviors: case-insensitive local parts, plus-addressing that ignores everything after the + symbol, and dots that carry no semantic meaning in the local part. Additional risks arise from IDNA homograph domains that visually mimic legitimate addresses but encode to different Punycode strings. Proper mitigation requires storing both the original email for delivery and a domain-aware normalized form for uniqueness checks, combined with explicit IDNA validation on registration.
Dangling DNS Records Expose Companies to Subdomain Takeovers Years After Projects Shut Down
A marketing team requested reactivation of a three-year-old promotional landing page, only to discover that its domain now served an unrelated third-party website. The root cause was a forgotten CNAME record in the company's DNS zone that continued pointing to a project name on external hosting after the original service had been decommissioned. Because many hosting providers use wildcard DNS entries, standard availability checks and simple DNS resolution tests fail to detect that the target project no longer exists. Attackers who re-register the freed project name can then serve content under the company's legitimate subdomain, automatically obtaining valid TLS certificates and inheriting domain-wide cookies. The article details how such dangling records accumulate across infrastructure, marketing, and acquired company zones, and explains the concrete risks including cookie theft, bypass of Content-Security-Policy, and unauthorized domain ownership proofs. It concludes with a practical remediation workflow: export the full zone, assign owners to every record, validate external targets by application response rather than DNS resolution, and embed record removal into decommissioning procedures.
Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has released an urgent update for Chrome to address CVE-2026-85046, a high-severity zero-day vulnerability in the V8 JavaScript engine that is being actively exploited in the wild. The flaw is a type confusion issue within the Maglev compiler, specifically tied to optimizations around Array.prototype.sort, which can lead to arbitrary memory read and write primitives inside the JavaScript heap. Attackers can exploit the vulnerability by tricking victims into visiting a specially crafted HTML page, enabling remote code execution within the browser sandbox. The update brings Chrome to version 152.0.7977.82 or higher on Windows, macOS, and Linux, while also addressing a total of 12 vulnerabilities. The issue was reported by researcher Salvatore Gulizia, known as Serotav, who received a $1,000 reward. Other Chromium-based browsers such as Edge, Brave, Opera, and Vivaldi will require corresponding updates from their vendors.
Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has released an urgent update for Chrome to address CVE-2026-85046, a high-severity zero-day vulnerability in the V8 JavaScript and WebAssembly engine that is being actively exploited in the wild. The flaw is a type confusion issue tied to the Maglev compiler and optimizations around Array.prototype.sort, which can lead to arbitrary memory read and write primitives inside the JavaScript heap. Successful exploitation allows a remote attacker to execute arbitrary code within the browser sandbox after a victim visits a specially crafted HTML page, a technique commonly seen in malvertising and compromised-site campaigns. The fix is included in Chrome 152.0.7977.82 and later for Windows, macOS, and Linux, and the update also resolves a total of twelve vulnerabilities. The vulnerability was reported on 4 August 2026 by researcher Salvatore Gulizia, known as Serotav, who received a $1,000 reward. Other Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi will require corresponding updates from their respective vendors.