CISA lists Cisco BroadWorks XXE flaw CVE-2026-20320 as exploited
An unauthenticated remote attacker can send a crafted XML message to the BroadWorks OCI-P service and read sensitive files with the privileges of the BroadWorks user.
What CISA added
On 2026-11-10 CISA added CVE-2026-20320 to its catalog of known exploited vulnerabilities (KEV). The entry is titled “Cisco BroadWorks Improper Restriction of XML External Entity Reference Vulnerability”, with Cisco as the vendor and BroadWorks as the product. It maps to CWE-611, improper restriction of XML external entity reference, better known as XXE. Known ransomware campaign use is listed as Unknown.
For US federal civilian agencies bound by BOD 22-01, the due date is 2026-11-24.
The NVD record itself is older: it was published on 2026-08-19 and now has the status Modified. The KEV listing in November means CISA has evidence of exploitation in the wild, which changes the priority of a flaw that has had a public advisory for months.
How the flaw works
According to NVD, the vulnerability is in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks. XML entries are improperly parsed because external entity resolution is allowed by default.
An attacker exploits it by sending a crafted XML message to the Open Client Interface Provisioning (OCI-P) service. No authentication is needed. If the parser resolves an external entity that points at a local file, the contents come back to the attacker. A successful exploit could allow the attacker to view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user. The KEV description summarizes the impact as reading sensitive configuration information on an affected system.
This is a read primitive, not code execution. On a provisioning interface, though, configuration files are exactly the data that can lead to further access.
Severity
The record carries a secondary CVSS 3.1 base score of 7.5 HIGH supplied by Cisco, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. That reads as a network attack vector, low complexity, no privileges required, no user interaction, unchanged scope, high impact on confidentiality and none on integrity or availability. The score fits the description: anyone who can reach the OCI-P service can read files, but cannot change them or take the system down through this bug alone.
What to do
The vendor reference is the Cisco security advisory cisco-sa-bworks-xxe-uwUd7CEt, linked from both the KEV notes and the NVD references.
The KEV required action is to apply mitigations in accordance with vendor instructions, following CISA’s BOD 26-04 guidance on prioritizing security updates based on risk and its “Forensics Triage Requirements”. Where mitigations are unavailable, the guidance is to follow the applicable BOD 26-04 guidance for cloud services or discontinue use of the product. Stakeholders are also responsible for evaluating each asset’s internet exposure.
Exposure is the practical first question here. Since the attack needs only network access to the OCI-P service, limiting who can reach that interface reduces the risk while the vendor fix is applied, and the forensics step matters because any configuration data that was readable before the fix should be treated as possibly exposed.
Source: CVE-2026-20320 (NVD, CISA KEV)