CISA placed Cisco BroadWorks CVE-2026-20320 on its KEV list November 10. The flaw lets an unauthenticated remote attacker read sensitive configuration information from an affected system. CISA lists November 24 as the due date for systems subject to its federal directive; other operators should find exposed systems and move to Cisco’s fixed release.

Cisco published its advisory on August 19. The November KEV addition changes the urgency for service providers and enterprise teams running BroadWorks Application Delivery Platform, Application Server, Profile Server or Xtended Services Platform on vulnerable releases. Cisco’s advisory still says its PSIRT is unaware of malicious use; CISA’s later catalog entry identifies the vulnerability as exploited.

XML parsing exposes BroadWorks files

The Open Client Interface, or OCI, processes XML for BroadWorks provisioning. Cisco says the parser allows external entity resolution by default. An attacker who reaches the OCI-P provisioning service can send a crafted XML message; the parser can read files with the privileges of the BroadWorks user. Cisco characterizes the technique as an out-of-band blind XML external entity flaw. The CVE Program record carries Cisco’s description and classifies the issue as CWE-611.

A service account’s readable files are the relevant prize. Configuration files can carry operational details or secrets, so a file-read flaw on a communications platform deserves attention beyond one end user. Cisco describes confidentiality impact, with no integrity or availability impact in its CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N vector.

Cisco names four affected components

Cisco lists Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform when they run a vulnerable BroadWorks release. Its scope is “regardless of device configuration.” On Application Delivery Platform, Cisco’s release-table footnote names Open Client Server (OCS) and OCIOverSoap. Cisco identifies RI.2026.07 as the first fixed release for each of the four components. Match each installed component and branch against the vendor’s fixed-release table, particularly the Application Delivery Platform footnote, before scheduling an upgrade.

Cisco says there is no workaround that addresses the vulnerability. Nulltap recommends limiting OCI-P to trusted provisioning systems while installing Cisco’s fixed release. That reduces the number of callers able to reach the vulnerable service.

Inventory access and install the fix

Start with the BroadWorks inventory: identify those four components, record installed releases and determine which OCI-P endpoints are reachable from the internet or untrusted networks. CISA expressly tells stakeholders to evaluate each asset’s internet exposure. Restrict provisioning access to the systems that need it, then plan Cisco’s fixed software on every affected component. Install the fixed release even for systems reachable only from private networks.

For teams subject to CISA’s KEV action, follow Cisco’s update instructions and the applicable BOD 26-04 patching and forensics-triage guidance by November 24; CISA also calls for cloud-service guidance or discontinuing use if mitigations are unavailable. Use your own provisioning-service access logs and network flow records to identify unexpected sources reaching OCI-P, and investigate suspicious file access under the BroadWorks service account where that telemetry exists. Check the installed build even if those logs are quiet.

After the upgrade, read each component’s installed release from the running system and compare it with Cisco’s table. Affected systems should show an appropriate fixed release, beginning with RI.2026.07, and only authorized provisioning systems should have network access to OCI-P. That is the operational check: a recorded installed build and a reachability test from outside the approved provisioning network.