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
Telegram Desktop Bug Deletes Up to 800 GB of User Data on Windows Due to Spellcheck Library Error
A critical configuration flaw in Telegram Desktop for Windows caused the application to recursively delete the entire contents of the C:\custom directory, resulting in the loss of approximately 800 GB of user data including programs, projects, and personal files. The issue originated in the lib_spellcheck library introduced in version 7.1.0, where an empty working directory path was concatenated with /custom and resolved by Qt into an absolute system path. Instead of locating a dictionary file, the code invoked removeRecursively() on the discovered directory, systematically erasing all accessible files while leaving folder structures intact. The bug affected only Windows builds with the built-in spellchecker enabled and remained in distribution for roughly 66 hours across versions 7.1.0 and 7.1.1. Researchers confirmed the behavior using Process Monitor logs and reported it via ticket #31170, prompting developers to add path validation before the function call and disable dictionary operations on empty paths. The corrected code was released in Telegram Desktop 7.1.2, and users running the vulnerable versions are advised to update immediately. No impact was observed on Linux or macOS platforms.
Essential Active Directory Checks Before Launching Any Penetration Test
Internal penetration tests of Active Directory can quickly generate noise in logs or disrupt services if techniques are applied without proper context. The article stresses that testers must first map domain boundaries, identify controllers, clarify allowed segments, and establish escalation procedures with the client. Detailed inventory of user, service, and privileged accounts is required, including analysis of Kerberos pre-authentication settings that enable AS-REP Roasting. Testers should also examine DACL permissions, delegation relationships, and Active Directory Certificate Services templates before attempting any exploitation. The guidance covers NTLM relay risks, the importance of maintaining an action log, and the distinction between standard pentests and Red Team engagements. A demo version of the Red September course on Active Directory attacks is offered to practice these steps in a controlled environment.
Microsoft Defender Misclassifies Legitimate Google Search Links as Threats
Microsoft is investigating a false positive issue in Defender for Office 365 where legitimate Google search result links are incorrectly flagged as unsafe. Users attempting to open these links receive a warning stating the website may be insecure, and the problem persists even when copying and pasting URLs directly into browsers. The incident, tracked under advisory MO1465962, stems from erroneous classification by the Safe Links feature, which rewrites and rechecks URLs in email, Teams, and Microsoft 365 applications. The misclassification affects not only end users but also generates alerts for administrators in the Microsoft Defender Portal and Microsoft Sentinel SIEM platform. Safe Links is designed to protect against phishing by validating links at click time, but in this case it overreacted by blocking entire Google search URLs. Microsoft has not disclosed the number of impacted customers or affected regions and continues working on a fix for the erroneous classification.
NVD Disruptions Force Security Teams to Diversify Vulnerability Intelligence Sources
The vulnerability management ecosystem has undergone major shifts over the past two years, undermining reliance on a single authoritative database. NVD, long considered the central enrichment layer for CVE records, has experienced significant operational problems that affect timeliness and completeness of data. Russian organizations are increasingly turning to BDU FSTEC as the national vulnerability database that provides official descriptions, remediation guidance, and coverage of domestic software. CVE maintained by MITRE continues to serve as the universal identifier standard, yet it lacks the detailed scoring and product mappings previously supplied by NVD. Vendor security bulletins from Microsoft, Cisco, Astra Group, and Positive Technologies often deliver the earliest and most accurate information. The article explains why a multi-source approach has become essential for comprehensive vulnerability management programs.