Skip to content
eastbaycyber

CVE-2026-20320: Cisco BroadWorks XXE Vulnerability

CVSS · Low
3.1
In CISA KEV
Yes
Published
Nov 20
Patch SLA & TriageVector: Network
Immediate (BOD 22-01 due 2026-11-24)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-20
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-10. Federal agencies must patch by 2026-11-24.

Everything CISA added on 2026-11-10 · Cisco KEV history

▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-20320 is an unauthenticated, remotely exploitable XML external entity (XXE) flaw in Cisco BroadWorks OCI-P. - BroadWorks releases earlier than RI.2026.07 are affected; upgrade to RI.2026.07 or later. - CISA lists the vulnerability in its Known Exploited Vulnerabilities catalog, with a 2026-11-24 remediation deadline. - Cisco says it has no complete workaround. Restricting network access can reduce exposure temporarily but does not fix the parser flaw.

What Is the Root Cause?

The root cause is CWE-611, improper restriction of XML external entity references. The BroadWorks OCI XML Parser permits external entity resolution by default.

In XML, an external entity can reference a local file or remote resource. If the parser resolves attacker-controlled declarations, the application may disclose data from the server’s filesystem or make outbound requests on the attacker’s behalf.

The attack requires network access to the OCI-P service but does not require credentials, a logged-in user, or interaction from another person. The attacker supplies crafted XML designed to trigger entity expansion or external resource resolution.

The precise file contents available to an attacker depend on the operating-system permissions and runtime privileges of the Cisco BroadWorks service account.

This is primarily a confidentiality vulnerability. Successful exploitation may expose sensitive configuration information and other readable local files. The supplied advisory information does not identify a mechanism for modifying files, changing BroadWorks configuration, or causing a denial of service.

Administrators should nevertheless treat disclosed credentials, tokens, topology data, and configuration secrets as potential stepping stones to further compromise.

Technical Notes

A generic XXE payload often contains a DOCTYPE declaration and an external entity reference. The following is a representative detection example, not a Cisco-provided exploit and not a recommendation to test production systems without authorization:

<?xml version="1.0"?>
<!DOCTYPE request [
  <!ENTITY xxe SYSTEM "file:///etc/hostname">
]>
<request>&xxe;</request>

Relevant defensive indicators include XML requests containing:

  • DOCTYPE
  • ENTITY
  • SYSTEM
  • PUBLIC

Blind XXE attempts may instead reference an attacker-controlled domain or IP address and may not place file contents in the immediate response.

AnalystImpact · assess the risk

What Happened?

CVE-2026-20320 is an improper restriction of XML external entity references in the Cisco BroadWorks Open Client Interface (OCI) XML Parser. The vulnerable functionality can process attacker-controlled XML with external entity resolution enabled by default.

A remote, unauthenticated attacker may send specially crafted XML to the Open Client Interface—Provisioning (OCI-P) service and read sensitive files accessible to the BroadWorks service account. This makes the Cisco BroadWorks vulnerability especially serious when OCI-P is reachable from the internet, partner networks, customer environments, or broad internal segments.

Field Details
CVE ID CVE-2026-20320
CVSS v3.1 7.5 High
CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Vulnerability type CWE-611, XML external entity reference restriction
Attack vector Network
Authentication required None
User interaction None
Affected functionality OCI-P, Open Client Server (OCS), and OCIOverSoap
Fixed version RI.2026.07
CISA KEV status Yes; added 2026-11-10
CISA remediation deadline 2026-11-24

Cisco’s fixed-release tables identify versions earlier than RI.2026.07 as affected for the listed product families.

CISA classifies CVE-2026-20320 as exploited in the wild. Cisco’s advisory update dated 2026-11-13 says Cisco does not have direct evidence of active exploitation. Defenders should preserve that distinction while treating the issue as an urgent remediation priority because of its KEV status.

Analyst’s take: Patch status and exposure should drive the first response, not the difference between CISA’s catalog classification and Cisco’s direct evidence. Inventory affected roles, identify reachable OCI-P services, and upgrade all pre-RI.2026.07 nodes.

For background on vulnerability terminology, see our guide to the difference between a vulnerability and an exploit.

Who Needs to Act?

Organizations operating Cisco BroadWorks Application Delivery Platform, Application Server, Profile Server, or Xtended Services Platform should inventory the running BroadWorks release.

Cisco identifies releases earlier than RI.2026.07 as affected for the listed products. The Application Delivery Platform entry specifically includes Open Client Server (OCS) and OCIOverSoap.

Product family Affected versions Fixed version
BroadWorks Application Delivery Platform, including OCS and OCIOverSoap Releases earlier than RI.2026.07 RI.2026.07
BroadWorks Application Server Releases earlier than RI.2026.07 RI.2026.07
BroadWorks Profile Server Releases earlier than RI.2026.07 RI.2026.07
BroadWorks Xtended Services Platform Releases earlier than RI.2026.07 RI.2026.07

Risk is highest for deployments where OCI-P is reachable from:

  • The public internet
  • Partner networks
  • Customer networks
  • Broad internal network segments
  • Compromised hosts or permitted integration zones

Internal-only exposure is not automatically safe. Telecommunications environments commonly contain multiple administrative, provisioning, and integration zones. A compromised host or partner account may provide network reachability without requiring application authentication.

Asset owners should account for clustered and geographically distributed deployments. Fixing one node does not remediate an affected pool if other Application Delivery Platform, Application Server, Profile Server, or Xtended Services Platform instances remain on an earlier release.

Record each node’s:

  • BroadWorks release
  • Product role
  • OCI-P exposure
  • Load-balancer or proxy path
  • Maintenance status

Why Is the CVSS Score 7.5 High?

CVE-2026-20320 has a CVSS v3.1 score of 7.5 High, represented by:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

The vector describes a vulnerability that can be exploited over the network (AV:N) with low attack complexity (AC:L). No privileges are required (PR:N), and no user interaction is needed (UI:N).

These characteristics make the vulnerability operationally serious, particularly when OCI-P is reachable from untrusted networks.

The scope remains unchanged (S:U) because the described impact occurs within the vulnerable BroadWorks security authority. Confidentiality impact is high (C:H) because exploitation can expose sensitive files and configuration data. Integrity and availability impacts are scored as none (I:N/A:N) based on the published description.

The score does not mean the issue is harmless to business operations. Leaked credentials, certificates, provisioning data, or topology information can enable follow-on attacks that are not directly represented in the base CVSS score.

Has CVE-2026-20320 Been Exploited?

CISA lists CVE-2026-20320 in the Known Exploited Vulnerabilities catalog. The catalog entry was added on 2026-11-10, with a remediation due date of 2026-11-24.

For defensive prioritization, organizations should treat the vulnerability as exploited in the wild and accelerate remediation, especially for internet-facing or otherwise untrustedly reachable OCI-P services.

Cisco’s advisory, updated on 2026-11-13, states that Cisco does not have direct evidence of active exploitation. That statement refers to Cisco’s own evidence and does not negate CISA’s catalog classification.

The available information also identifies a Malbear Labs report, referenced by the NVD record, describing “Operation Snowball” and alleged attacks involving a European telecommunications provider and organizations hosted on its infrastructure. That report should be treated as contextual threat reporting rather than a Cisco-confirmed technical exploit demonstration.

No verified, directly linked public proof-of-concept repository was identified in the supplied primary or vendor materials.

The current status should therefore be recorded precisely:

  • CISA KEV status indicates exploitation in the wild.
  • Cisco reports no direct evidence of active exploitation.
  • No verified public PoC repository has been confirmed here.
  • Known ransomware campaign use is unknown.
ResponderRunbook · act now

Detection Guidance

Start with exposure identification rather than waiting for a reliable exploit signature.

  1. Inventory BroadWorks nodes.
  2. Compare their releases with RI.2026.07.
  3. Confirm whether OCI-P, OCS, or OCIOverSoap listeners are reachable from untrusted networks.
  4. Review load balancers, firewalls, reverse proxies, and service maps.
  5. Investigate suspicious XML requests and outbound connections.

Direct host scans may miss exposure behind an intermediary, so review the complete traffic path.

For a broader understanding of security controls and governance relevant to vulnerability response, see our ISO 27001 glossary guide.

Log and Request Indicators

Review OCI-P and adjacent proxy or load-balancer logs for unauthenticated XML requests containing:

  • External entity syntax
  • Unusual DOCTYPE declarations
  • ENTITY, SYSTEM, or PUBLIC declarations
  • file:// references
  • External URLs
  • Unexpected XML request structures

Blind XXE attempts may generate DNS or HTTP traffic to an attacker-controlled system even when the application response does not contain file contents.

Also investigate:

  • Access to sensitive files
  • Unexpected BroadWorks service-account behavior
  • New outbound connections
  • Exposed credentials or tokens
  • Changes to network or provisioning activity

A practical starting point for web, proxy, or normalized request logs is a case-insensitive search for XML external entity indicators:

zgrep -Eai 'DOCTYPE|ENTITY|SYSTEM[[:space:]]+["'\'']|PUBLIC[[:space:]]+["'\'']' \
  /var/log/*access*.log /var/log/*proxy*.log 2>/dev/null

This pattern is heuristic and may produce false positives. Adapt it to the actual BroadWorks logging format and validate it against known-good provisioning traffic.

If logs are shipped to a SIEM, an equivalent query could be expressed as:

http.request.body:(DOCTYPE OR ENTITY OR "SYSTEM " OR "PUBLIC ")
AND service:(OCI-P OR OCIOverSoap OR OCS)

Use the product’s actual service labels and field names in production. Alert on requests that combine XML declaration syntax with unauthenticated access, external URLs, file:// references, or outbound DNS/HTTP connections from BroadWorks hosts.

Network Telemetry

Investigate BroadWorks nodes making new outbound DNS or HTTP connections to unfamiliar domains shortly after receiving an OCI-P XML request.

A useful correlation window is the request timestamp plus several minutes, adjusted for the environment’s normal processing latency.

No Cisco-specific network signature was provided, so this behavioral approach should supplement—not replace—patching.

Remediation and Patching

Upgrade affected systems to BroadWorks RI.2026.07 or a later fixed Cisco-supported release.

This applies to the affected:

  • Application Delivery Platform
  • Application Server
  • Profile Server
  • Xtended Services Platform

Include all nodes and roles in the upgrade plan, including systems supporting OCS and OCIOverSoap. Verify the resulting release after maintenance and retain evidence for the vulnerability record.

Cisco states that no workaround fully addresses this vulnerability.

If an immediate upgrade is impossible, treat network restriction as temporary risk reduction rather than remediation. Recommended interim measures include:

  • Limit OCI-P access to trusted management or provisioning networks.
  • Remove unnecessary internet exposure.
  • Restrict permitted source addresses.
  • Review outbound egress from BroadWorks servers.
  • Monitor for suspicious XML and external network activity.

These controls may reduce exploitability but cannot correct the parser behavior. They may also fail to prevent exploitation by a permitted or compromised internal source.

The CISA KEV deadline is 2026-11-24. Organizations subject to applicable CISA guidance, including relevant federal environments, should follow the required risk-based security-update process and document exceptions.

If a hosted or cloud-managed BroadWorks deployment cannot be patched by the operator, escalate to the service provider. Determine whether continued use is appropriate when required remediation or effective containment is unavailable.

Upgrade Checklist

The precise upgrade workflow is deployment-specific and should follow Cisco’s supported BroadWorks maintenance procedures.

The concrete remediation target is:

Current release: any BroadWorks release earlier than RI.2026.07
Target release:  RI.2026.07 or later

Before upgrading, capture the current release and affected roles through the organization’s approved BroadWorks administration or inventory process.

After upgrading:

1. Inventory Application Delivery Platform, Application Server,
   Profile Server, and Xtended Services Platform nodes.
2. Record each node's BroadWorks release and OCI-P/OCS/OCIOverSoap role.
3. Upgrade each affected node to RI.2026.07 or later.
4. Drain and validate clustered nodes according to Cisco procedures.
5. Confirm no pre-RI.2026.07 node remains in service.
6. Recheck firewall, load-balancer, and DNS exposure.

If emergency containment is required before the upgrade, restrict inbound access to OCI-P at the firewall or proxy layer:

Allow: approved provisioning-management source networks -> OCI-P
Deny: all other source networks -> OCI-P
Review: BroadWorks outbound DNS/HTTP egress and unusual destinations

The exact ports and service identifiers depend on the deployment and were not specified in the supplied advisory material. Do not deploy an assumed port-based rule without confirming the local BroadWorks configuration.

Cisco has not identified this access restriction as a complete workaround.

After remediation, rotate credentials, tokens, or certificates if logs or forensic review indicate that sensitive files may have been disclosed. Preserve relevant logs before rotation, investigate suspicious outbound connections, and assess whether exposed configuration data could enable access to other telecommunications systems.

References

  1. Cisco security advisory: Cisco BroadWorks XML External Entity Injection
  2. Cisco CSAF/CVRF advisory data
  3. CISA Known Exploited Vulnerabilities catalog
  4. NVD record for CVE-2026-20320
  5. Malbear Labs: “Operation Snowball”

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-20

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.