Cisco BroadWorks: Exploited Flaw CVE-2026-20320
Published November 13, 2026 · Last updated November 13, 2026
What happened: On November 10, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-20320, a flaw in Cisco BroadWorks, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "Cisco BroadWorks Improper Restriction of XML External Entity Reference Vulnerability."
CISA's summary: "Cisco BroadWorks contains an improper restriction of XML external entity reference vulnerability that could allow an unauthenticated, remote attacker to read sensitive configuration information on an affected system."
CVE-2026-20320 is a flaw in Cisco BroadWorks, the calling platform that phone and cloud communications providers run to deliver hosted voice and collaboration services to their business customers. It lets an attacker who has no account read sensitive files from an affected server. Cisco first published its advisory on August 19, 2026. On November 10, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added the bug to its Known Exploited Vulnerabilities (KEV) catalog, with a due date of November 24, 2026. CISA lists known ransomware campaign use as "Unknown."
That makes a three-month-old fix urgent again. If your organization operates BroadWorks and has not installed the August update, this is the week to do it.
What goes wrong
BroadWorks exposes a programming interface called the Open Client Interface (OCI). Its provisioning flavor, OCI-P, accepts XML messages that create and change users, groups and services. According to Cisco's advisory, the XML parser behind that interface allows "external entity resolution" by default.
That setting is the root of a well-known class of bug called XML external entity injection, or XXE (the CVE record classifies it as CWE-611, improper restriction of XML external entity reference). An XML message can contain a reference that tells the parser to fetch outside content, such as a file on the server's own disk, and fold it into the document. When a parser honors those references from untrusted input, a crafted message can make the server hand back data it was never supposed to share.
Cisco says an attacker could exploit the bug "by sending a crafted XML message" to the OCI-P service, and that a successful attack "could allow the attacker to view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user." CISA's catalog describes the impact as reading "sensitive configuration information." The attack is remote and needs no login.
Configuration files on a calling platform can include details an intruder would value, such as connection settings for other systems. Neither Cisco nor CISA lists which files were exposed in any real attack, so treat that as the kind of risk to assess, not a reported finding.
Who is affected
Cisco lists four products as vulnerable when running an affected release, "regardless of device configuration":
- BroadWorks Application Delivery Platform
- BroadWorks Application Server
- BroadWorks Profile Server
- BroadWorks Xtended Services Platform
For the Application Delivery Platform, a footnote in the advisory ties the issue to the Open Client Server (OCS) and OCIOverSoap components. Cisco states that only the products in this list are known to be affected.
End users of a hosted phone service cannot patch anything themselves. The work falls on the service providers and enterprises that run the BroadWorks servers.
The fix
For all four products, Cisco names the same first fixed release: RI.2026.07. Any release earlier than RI.2026.07 is affected. Cisco "strongly recommends" moving to the fixed software and says it treats any workaround or mitigation as temporary until an upgrade is done.
There are no workarounds. Cisco states this twice in the advisory, so disabling a setting is not an option; the upgrade is the remedy. Network controls that keep the OCI-P service reachable only from trusted provisioning systems can reduce exposure while an upgrade is scheduled, but Cisco does not offer that as a fix.
Was it exploited? Cisco and CISA differ
The advisory's revision history shows how the exploitation question has moved this week:
- Version 1.0, August 19, 2026: initial public release.
- Version 1.1, November 12, 2026: updated "to reflect known active exploitation."
- Version 1.2, November 13, 2026: corrected to say the bug was added to CISA's KEV catalog, adding that "Cisco does not have direct evidence of active exploitation."
CISA's position is different. Inclusion in KEV means CISA has reliable evidence of exploitation in the wild, and its decision data on the CVE record, dated November 10, marks exploitation as "active," automation as "yes," and technical impact as "partial." In plain terms, CISA rates it as already used by attackers, easy to repeat at scale, and limited in how much of the system it exposes. Neither source publishes attacker names, victim counts or technical indicators.
The practical answer is the same either way: an unauthenticated file-read bug on a carrier calling platform, listed in KEV, should be patched now.
Severity and who scored it
Cisco, the CVE Numbering Authority for its own products, scored the flaw CVSS 3.1 7.5 (High), vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. NVD lists that Cisco score as a Secondary source and had not published a Primary score of its own when we checked. The vector reflects network access, low complexity, no privileges, no user interaction, and high impact on confidentiality only. It does not claim the attacker can change data or crash the system.
What to do
- Service providers and enterprises running BroadWorks: upgrade the Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform to RI.2026.07 or later.
- While the upgrade is pending: confirm that the OCI-P interface is not reachable from the internet or from untrusted networks. This is a risk reducer, not a Cisco-endorsed workaround.
- Security teams: because KEV lists the bug as exploited, review OCI-P request logs for unexpected XML from unfamiliar sources, and consider rotating credentials or keys stored in configuration files on exposed servers.
- U.S. federal agencies: the KEV entry says to apply mitigations according to vendor instructions by November 24, 2026, following CISA's BOD 26-04 guidance and its forensics triage requirements, or to stop using the product if mitigations are unavailable.
- Businesses that buy hosted calling: you cannot fix this yourself. It is reasonable to ask your provider whether its BroadWorks platform is on RI.2026.07.
Timeline
- August 19, 2026: Cisco publishes advisory cisco-sa-bworks-xxe-uwUd7CEt and the CVE record.
- November 10, 2026: CISA adds the flaw to the KEV catalog.
- November 12, 2026: Cisco updates the advisory to reflect exploitation.
- November 13, 2026: Cisco revises the advisory to say it has no direct evidence of exploitation and cites the KEV listing.
Cisco credits Sandesh M Gawai with reporting the vulnerability.
Sources: Cisco Security Advisory cisco-sa-bworks-xxe-uwUd7CEt; the CISA Known Exploited Vulnerabilities catalog; the CVE record published by Cisco; NVD.
What the National Vulnerability Database says
NVD first published CVE-2026-20320 on August 19, 2026. Its description, from the record's source ([email removed]), reads: "A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticated, remote attacker to read sensitive configuration information on an affected system. This vulnerability exists because XML entries are improperly parsed due to external entity resolution being allowed by default. An attacker could exploit this vulnerability by sending a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service. A successful exploit could allow the attacker to view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user."
How serious is CVE-2026-20320?
The CVSS 3.1 base score is 7.5 out of 10 (High), scored by cisco.com. In plain terms: an attacker can reach the BroadWorks weakness over a network, including the internet; the attacker does not need an account; no one has to click or open anything. The listed impact on BroadWorks data secrecy is high, on data integrity none, and on availability none. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
Which BroadWorks versions are affected?
The CVE record lists these affected ranges:
- broadworks application delivery platform before ri.2026.07
- broadworks application server before 2026.0
- broadworks profile server before 2026.07
- broadworks xtended services platform before 2026.07
If your BroadWorks version falls in one of these ranges, check Cisco's advisory for the fixed release that applies to you.
What kind of weakness is it?
CISA and NVD map CVE-2026-20320 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):
- CWE-611: Improper Restriction of XML External Entity Reference. MITRE's definition: "The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output."
CISA required action for CVE-2026-20320
CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "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."
Timeline for CVE-2026-20320
- August 19, 2026: NVD publishes CVE-2026-20320.
- November 10, 2026: CISA adds CVE-2026-20320 to the KEV catalog.
- November 13, 2026: latest change to the NVD record (status: Modified).
- November 24, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-20320.
Advisories and technical references
The NVD record for CVE-2026-20320 links to these references; tags in brackets are NVD's labels:
- sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe- (Vendor Advisory)
- malbearlabs.com/posts/operation-snowball-inside-an-autonomous-ai-intrusion-campaign (Exploit, Third Party Advisory)
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-20320 (US Government Resource)
What to do
- Run Cisco BroadWorks? Follow Cisco's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
- Federal civilian agencies must act by November 24, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for BroadWorks too.
- Ransomware use: CISA lists known ransomware campaign use for CVE-2026-20320 as "Unknown".
- Don't run BroadWorks yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-20320" and asks for payment or remote access, that is a scam pattern, not a Cisco alert.
CVE-2026-20320 record details from CISA and NVD
- CISA forensic triage flag for CVE-2026-20320: No
- Attack complexity for CVE-2026-20320: low
- CVE-2026-20320 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-20320: exploitability 3.9, impact 3.6.
- Who mapped the weakness type: the address listed on cisco.com (Secondary)
- NVD product identifiers (CPE):
cpe:2.3:a:cisco:broadworks_application_delivery_platform:*:*:*:*:*:*:*:*,cpe:2.3:a:cisco:broadworks_application_server:*:*:*:*:release_independent:*:*:*,cpe:2.3:a:cisco:broadworks_profile_server:*:*:*:*:release_independent:*:*:*,cpe:2.3:a:cisco:broadworks_xtended_services_platform:*:*:*:*:release_independent:*:*:* - References in the NVD record: 3 (1 tagged Vendor Advisory, 1 tagged Exploit, 1 tagged Third Party Advisory).
- CISA SSVC decision points for CVE-2026-20320 (from NVD): exploitation=active; automatable=yes; technicalImpact=partial (role: CISA Coordinator, SSVC 2.0.3).
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.