Cisco BroadWorks unauthenticated XXE exploited to read files, now in CISA KEV
An unauthenticated XXE in the BroadWorks OCI-P XML parser lets remote attackers read configuration and files. CISA lists it as exploited. Upgrade every BroadWorks component to RI.2026.07, and rotate keys on systems that were exposed.
CISA added the flaw to KEV on 2026-11-10. Two days earlier, Malbear Labs reported it as the entry point into a European telecom provider's BroadWorks XSP. Cisco's advisory has not been updated to confirm exploitation.
What you need to know
- Affects BroadWorks Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform before RI.2026.07, regardless of configuration.
- An unauthenticated remote attacker who can reach the OCI-P service can read configuration and files with the BroadWorks user's privileges.
- Exploited in the wild: in CISA KEV since 2026-11-10 (federal due date 2026-11-24), and used against a European telecom provider in Malbear's Operation Snowball report.
- Upgrade all four components to RI.2026.07 or later. Cisco offers no workaround. Rotate the system identity key and SSL keys on hosts that were exposed before patching.
- Hunt for unexpected outbound connections from BroadWorks hosts, and check egress and DNS logs against the Operation Snowball infrastructure.
What's happening
CVE-2026-20320 is an out-of-band blind XML External Entity (XXE) injection in the Open Client Interface (OCI) XML parser of Cisco BroadWorks 1. A remote attacker with no credentials can send a crafted XML message to the OCI-Provisioning (OCI-P) service and read sensitive configuration and filesystem contents as the BroadWorks user 1. Cisco published the advisory and the fixed release RI.2026.07 on 2026-08-19 and rated the flaw CVSS 7.5 1.
The Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform are all affected before RI.2026.07, whatever their configuration 1. Practical exposure depends on whether an attacker can reach OCI-P. Cisco lists no workarounds 1.
CISA added the CVE to its Known Exploited Vulnerabilities catalog on 2026-11-10, with a federal remediation date of 2026-11-24 2,3,6. The public account of exploitation comes from Malbear Labs, which reported on 2026-11-08 that an autonomous AI intrusion harness used the flaw to enter a European telecom provider through its BroadWorks XSP 4,5. Thirteen organizations hosted on that provider's infrastructure were in scope 4. Malbear describes the operator only as Chinese-speaking, and no vendor or government has named an actor 4. Coverage by The Hacker News and SecurityWeek draws on Malbear and CISA rather than independent telemetry 5,6.
How it works
The bug is CWE-611, improper restriction of XML external entity references 1. Cisco attributes it to the OCI XML parser resolving external entities by default, so attacker-supplied entity declarations in an OCI-P message get processed 1. Because the flaw is blind and out-of-band, file contents do not come back in the protocol response. Data instead leaves through a connection the parser makes to infrastructure the attacker controls, which is why egress monitoring matters.
Exploitation needs network access to OCI-P and no authentication or user interaction 1. Impact is limited to confidentiality: integrity and availability are not affected in the CVSS scoring 1. Even so, readable files on a BroadWorks host can include key material. In the documented intrusion, the agent recovered the XSP's system identity private key, three SSL credential sets and three more private keys 4,5. Malbear notes the identity key lets an attacker impersonate the XSP in communication between BroadWorks components 4,5.
The victim XSP ran release 23.0.1.1075 with the OCI service reachable on TCP 2208 5. That is one deployment, and the sources do not map it to the RI release scheme. The wider campaign took subscriber billing and device records over about two weeks. It also used Sliver, Chisel, the Behinder web shell and exploits for many other products, so not all of that activity traces back to this flaw 5.
What to do
In order of priority- 1
Upgrade every BroadWorks ADP, Application Server, Profile Server and Xtended Services Platform to RI.2026.07 or later. Cisco states no workaround addresses the flaw 1.
- 2
Under CISA's KEV listing, US federal agencies must apply vendor mitigations by 2026-11-24, or stop using the product if mitigations are unavailable 2,6.
- 3
Until patched, limit OCI-P access to known provisioning clients on trusted networks, and block internet access to the service. This is exposure reduction, not a vendor-endorsed fix.
- 4
If OCI-P was reachable by untrusted parties before patching, assume the host's files were read. Rotate the system identity private key, SSL certificates and other private keys stored on BroadWorks hosts, since these were stolen in the observed intrusion 4,5.
- 5
On previously exposed systems, run a forensic review for Sliver, Chisel and Behinder artifacts and for lateral movement from BroadWorks hosts 5. Check egress logs for the published campaign infrastructure 4.
Detection
- Cisco publishes no detection guidance, signatures or IOCs for this CVE 1. The hunts below are defender guidance built from the campaign reporting.
- Inventory every BroadWorks ADP, Application Server, Profile Server and XSP node and confirm it runs RI.2026.07 or later 1. Treat anything older as exposed.
- Map where OCI-P can be reached from. The observed victim exposed the OCI service on TCP
22085. Flag any listener reachable from the internet or untrusted segments. - Review OCI-P request logs for unauthenticated messages containing
DOCTYPEorENTITYdeclarations, especially from sources other than known provisioning clients. - Alert on outbound HTTP, FTP or DNS from BroadWorks servers to unfamiliar hosts. Blind out-of-band XXE exfiltrates data through such callbacks.
- Search egress, proxy and DNS logs for the Operation Snowball infrastructure listed under IOCs 4. The published list may be incomplete.
- On BroadWorks hosts and adjacent systems, look for Sliver implants, Chisel tunnels and the Behinder web shell, which this campaign used 5.
Indicators
As published by the cited sources| Type | Value | Context |
|---|---|---|
| domain | api.tablacysexplorer[.]com | Sliver C2 beacon domain (port 443), Cloudflare-fronted. Campaign-level, not specific to this CVE.4 |
| ip | 113.23.212[.]15:8000 | Tool download server that served tool tarballs to the harness. Campaign-level.4 |
| ip | 212.46.38[.]73:56777 | Operator's secondary machine, used to reach the Sliver team server over an SSH tunnel. Campaign-level.4 |
Timeline
Cisco publishes advisory cisco-sa-bworks-xxe-uwUd7CEt with fixed release RI.2026.07 and reports no known malicious use. 1
Malbear Labs publishes 'Operation Snowball', documenting exploitation of the flaw against a European telecom provider's BroadWorks XSP. 4
CISA adds CVE-2026-20320 to the Known Exploited Vulnerabilities catalog. 2
KEV remediation due date for US federal agencies. 2
Sources
- 1Cisco BroadWorks Out-of-Band Blind XML External Entity Injection VulnerabilityCisco · Vendor · Aug 19, 2026
- 2CISA KEV entry for CVE-2026-20320CISA · Government · Nov 10, 2026
- 3CISA Adds Six Known Exploited Vulnerabilities to CatalogCISA · Government · Nov 10, 2026
- 4Operation Snowball: Inside an Autonomous AI Intrusion CampaignMalbear Labs · Research · Nov 8, 2026
- 5Cisco BroadWorks and Openwave Flaws Actively Exploited Despite Available PatchesThe Hacker News · News
- 6Threat Actors Exploit Openwave, Cisco BroadWorks VulnerabilitiesSecurityWeek · News · Nov 11, 2026
Corroborated by independent sources. Researched and drafted by the VulnDigest briefs agent from 6 sources, then checked against them by a separate review step on Nov 12, 2026.
Cisco has not confirmed exploitation. Its only advisory version (2026-08-19) came out before the reports. The evidence is CISA's KEV listing and Malbear Labs research.
Cisco's table shows 'RI.2026.071' for Application Delivery Platform. The trailing '1' is a footnote marker (OCS and OCIOverSoap). The first fixed release is RI.2026.07 for all four components.
Details of the XSP compromise (release, port, stolen keys) come from Malbear Labs as quoted by The Hacker News.
The IOCs are campaign-level, not specific to this CVE. The list includes only values confirmed in Malbear's report and may be incomplete.
No public proof-of-concept was confirmed. The first exploitation date is unknown; the campaign ran about two weeks before 2026-11-08.
The operator is described only as Chinese-speaking. No vendor or government has attributed the activity to a named actor.
Spotted an error? Open an issue on sochub.io.