Executive Summary

CVE-2026-20320 is an XML external entity (XXE) flaw in the Open Client Interface (OCI) XML parser of Cisco BroadWorks, where external entity resolution is enabled by default and lets an unauthenticated remote attacker send a crafted message to the OCI-Provisioning (OCI-P) service to read arbitrary files from the host filesystem. For operators who depend on BroadWorks for voice and provisioning of operational communications, this exposes stored credentials, configuration, and integration secrets that can be pivoted toward control and dispatch infrastructure.

Technical Exposure Breakdown

The defect is a classic XXE. The OCI XML parser resolves external entities declared in inbound XML documents. An attacker constructs an XML payload containing an entity that references a local file path, submits it to the OCI-P service, and the parser dereferences that path and returns the file contents in the response or through an out-of-band channel. No authentication is required and the attack is fully remote over the provisioning interface.

The precondition is simple network reachability to the OCI-P service. There is no privilege requirement and no user interaction. The read occurs with the privileges of the BroadWorks process, which typically means access to provisioning data stores, service configuration, and any credential material readable by that account. The grounding data lists the following affected ranges:

The assigned CVSS score is 7.5. This is flagged in the known exploited vulnerability catalog, which means it should be treated as under active exploitation rather than theoretical. Patch status in our grounding data is unknown, so do not assume a fix is available for your specific build. Confirm directly with the vendor before planning remediation windows.

OT Impact and Compliance Risk

BroadWorks is a telephony and unified communications platform, not a PLC, but in utility and pipeline environments it frequently sits adjacent to operational communications: dispatch lines, SCADA voice alarms, field crew coordination, and emergency notification. An attacker reading configuration files extracts the integration points. Those files commonly contain service account credentials, LDAP or RADIUS bind secrets, database connection strings, and API tokens that tie the comms platform into identity and operational systems. The file disclosure itself does not stop a turbine, but the harvested secrets are the lateral movement fuel toward systems that do.

From a compliance standpoint, if this platform resides inside an Electronic Security Perimeter, NERC CIP-005 and CIP-007 expect inbound access to be controlled and the system to be patched or risk-mitigated with documentation. Credential exposure cascades into CIP-004 and CIP-005 access control failures. Water utilities operating under AWIA 2018 should treat exposed dispatch and notification infrastructure as part of the risk and resilience assessment. Pipeline operators under TSA SD-02C must account for communications systems that bridge IT and OT zones. Under IEC 62443, a flat zone that exposes OCI-P to lower-trust networks is a zone and conduit failure independent of the CVE.

Compensating Controls

Do not run an active vulnerability scanner against production BroadWorks nodes on a shared OT segment without a maintenance window. Aggressive XML probing against the OCI-P service can crash the parser or exhaust the process, and collateral scanning of adjacent industrial components can disrupt or brick fragile devices.

BreachSpider Intel

BreachSpider tracks exploitation signals and affected version mappings for CVE-2026-20320 across the catalog so OT teams can scope exposure without scanning live control-adjacent systems.