CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Called exploited 46 days after disclosure.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listing46d
- Last KEV listing1d
- Last sighting2d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Sep 2, 2026
- EUVDENISA, European Unionlisted Sep 2, 2026
- VulnCheck KEVcommercial researchlisted Sep 1, 2026
- CIRCLaggregator, mirrors the abovelisted Sep 1, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationdashboard.shadowserver.org/statistics/honeypot/vulnerability
- reported exploitationeuvd.enisa.europa.eu/enisa/EUVD-2026-45205
- reported exploitationwww.cisa.gov/sites/default/files/feeds/known_exploited_vulne
- reported exploitationhorizon3.ai/attack-research/disclosures/cve-2026-9586-sangom
- reported exploitationprevidian.com/CVE-2026-9586
- reported exploitationx.com/DefusedCyber/status/2094790121505604074
7 public reports collected from VulnCheck and CIRCL, first on Sep 1, 2026. Each links to its original source. We have not verified them.
Description
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.
Required action (CISA)
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.
