CVE-2026-9586: Sangoma Switchvox

What is CVE-2026-9586?

An unauthenticated SQL injection vulnerability exists in Sangoma Switchvox SMB Edition 8.3 (104997). The /pa endpoint processes XML content beginning with <PolycomIPPhone> and directly concatenates the user-controlled PhoneIP value into PostgreSQL queries without sanitization or parameterization. An unauthenticated remote attacker can execute arbitrary SQL statements against the backend PostgreSQL database using a single crafted request, including database operations and remote code execution.

CVSS9.8 NVD 3.1

SeverityCRITICAL

Exploitation In the wild In CISA KEV

EPSS12% · P96

Triage statusActive Exploit

ActionPatch immediately

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWECWE-89

NVD published2026-07-17

NVD last modified2026-09-03

Timeline

2026-07-17Published to the U.S. National Vulnerability Database (NVD)
2026-09-02Added to the CISA Known Exploited Vulnerabilities (KEV) catalog
2026-09-03First covered in a defend.network daily briefing
2026-09-03NVD record last updated
2026-09-05CISA federal remediation deadline (BOD 22-01)

CISA Known Exploited Vulnerability

Sangoma Switchvox SQL Injection Vulnerability

Added to KEV2026-09-02

Federal patch deadline2026-09-05

Known ransomware useUnknown

Affected product

Sangoma Switchvox

Remediation Steps

Apply the vendor security update for Sangoma Switchvox as a priority.
Restrict network exposure of the affected service to trusted sources until patched.
Review logs and detections for indicators of exploitation.
Confirm fixed versions against the official vendor advisory before deploying.

References

Referenced in our briefings & reports

Vulnerability Priority Report – Week 5 of August 2026 (August 31 – September 6)
Critical RCEs in Switchvox, WordPress plugins; Windows Defender disablement campaign (2026-09-03)

Browse all tracked CVEs in the defend.network CVE database →

🤖 This CVE page is generated by defend.network from NVD, CISA KEV, EPSS, and our verified daily briefings. Severity and exploitation data come from official sources; always verify remediation steps against the official vendor advisory before acting in production.