← Back to CVE intelligence
CVE intelligenceCISA KEV

CVE-2026-9586

Sangoma Switchvox SQL Injection Vulnerability

Published Jul 17, 2026Sources checked Nov 20, 2026
9.8CRITICALCVSS out of 10
What this means

Actively exploited

CISA lists CVE-2026-9586 in its Known Exploited Vulnerabilities catalog, which means exploitation has been observed. The entry applies to Sangoma Switchvox.

  • Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Public exploit: Not collected.

What to do next

Remediation and response

  • Upgrade through Sangoma's supported path to Switchvox 8.4.0.2 or a later fixed release, and investigate evidence of earlier exploitation.
CISA KEVListedObserved exploitation
EPSS19.0%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors1Source-linked actor relationships
Research brief

Exposure, fixes and investigation

Reviewed

Source checks found no changes since the last completed research review.

Research source checks

Which deployments need attention?

An attacker who can reach the vulnerable Switchvox /pa endpoint does not need an account. SRA demonstrated the issue on 8.3 build 104997; NVD lists a broader affected range beginning at 8.2.2.1. Sangoma identifies 8.4.0.2 as the fix. [2] [4] [1]

Affected versions and fixes

First fixed releases listed by the sources. Follow the vendor's supported upgrade path.
ProductAffected versionsFirst fixed release
Sangoma Switchvox on-premises8.2.2.1 up to, but excluding, 8.4.0.2 (NVD range)8.4.0.2 (build 105309) [4] [1]

How the vulnerability works

The phone application handler inserts the XML PhoneIP value into a PostgreSQL query without adequate validation. The database runs with sufficient privileges for injected SQL to execute operating-system commands. This turns an unauthenticated SQL injection into appliance code execution. [2]

Reported attack activity

Horizon3.ai's September 1 disclosure describes exploitation attempts seen on Defused Cyber honeypots on August 30, after Sangoma's July 14 patch. The observations included commands intended to open a reverse shell. They do not identify a compromised customer deployment. [3]

Indicators and log locations

Reported attacker infrastructure
176.65.148.184

Horizon3.ai reports this address in August 30 honeypot activity. Correlate historical connections with other evidence; current ownership or activity may differ. [3]

Reported 2026-09-01
Investigation log location
/var/log/switchvox/db-quirks.log

The research identifies this log as a place to inspect SQL injection evidence when SSH access is available. The file path itself is not an indicator of compromise. [3]

Reported 2026-09-01

Investigation steps

SecurityAlert guidance

Upgrade through Sangoma's supported path to a fixed release. Check its hardware and upgrade prerequisites before moving older installations to 8.x. If immediate patching is impossible, restrict access to the affected service while preserving required phone connectivity and arranging the update. [1] [2]

Preserve available HTTP, database and network logs. Correlate unusual /pa requests with SQL errors, unexpected command execution and outbound connections. Review the period before patching; ordinary phone requests to /pa alone are not evidence of an attack. [2] [3]

Verify the update

SecurityAlert guidance

Capture the installed version and build after the supported update, verify each appliance and test normal phone service. If execution is suspected, preserve evidence and investigate persistence and exposed credentials before closing the incident. A successful update does not resolve that investigation. [1]

What the sources do not establish

SecurityAlert assessment

A historical IP match requires investigation, and no match does not establish a clean appliance. The neighboring Switchvox CVEs in the vendor bulletin have separate conditions; this record does not apply CVE-2026-9586 attack observations to them. [3] [1]

Sources for this brief (4)
  1. Sangoma 8.4.0.2 release notes
  2. SRA original Switchvox advisory
  3. Horizon3.ai Switchvox research
  4. NVD Switchvox record

Reviewed guidance supplements the live CVE feeds. It does not verify the state of your systems.

Publisher research

Version guidance and technical research

Collected from the publisher for this CVE. Check the source for configuration requirements and supported upgrade paths.

Sangoma

Vendor-listed versions for CVE-2026-9586. A fixed release does not establish the state of your systems.
ProductAffected versionsFixed release
Sangoma SwitchvoxVendor-listed affected version: 8.2.2.1. Complete range not specified.8.4.0.2

On-premises and Cloud. Listed under Issues Resolved; follow the supported upgrade prerequisites.

Read Sangoma: Switchvox - Release Notes Version 8.4.0.2 July 14, 2026

Last successful check: 2026-11-20 06:15 UTC.

Overview

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.

Source: NVD

Reported activity

The Hacker News reports attacks targeting CVE-2026-9586. The collected report supports exploitation attempts; it does not establish successful compromise.

The Hacker News · Published Sep 2, 2026
CISA says:Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.CISA catalog due date Sep 5, 2026