CISA Adds Cisco BroadWorks XXE Flaw to KEV Catalog, Patch by Nov. 24

An unauthenticated, remote XXE flaw in Cisco BroadWorks' OCI-P interface lets attackers read sensitive files. CISA says fix it by November 24.

The Cisco Systems logo
Image: Wikimedia Commons.

The Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-20320, a high-severity XML External Entity (XXE) injection flaw in Cisco BroadWorks, to its Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026. The bug lets an unauthenticated remote attacker send crafted XML to BroadWorks' Open Client Interface and pull sensitive files — potentially including configuration data and credentials — off the server. Federal civilian agencies running BroadWorks have until November 24, 2026 to patch or disconnect it, per CISA's KEV entry.

Cisco BroadWorks isn't a product most people have heard of, but it's the software running behind the scenes at a large number of phone and internet providers. If your business gets its hosted VoIP, video conferencing, or unified-communications service from a telecom carrier rather than running its own phone system, there's a decent chance BroadWorks is part of the plumbing. That's who needs to pay attention to this one — not home broadband customers.

This article walks through what the vulnerability actually does, why an "out-of-band blind" XXE bug is harder to notice than a standard one, which specific BroadWorks components and versions are affected, what Cisco's advisory does and doesn't confirm about active exploitation, and exactly what network operators need to do before the federal deadline hits.

What CISA Added to the KEV Catalog

CISA's KEV catalog is the federal government's list of vulnerabilities it has confirmed are being exploited, and Binding Operational Directive 22-01 requires Federal Civilian Executive Branch agencies to remediate anything on it by the stated due date. CVE-2026-20320 is the newest entry tied to carrier telecom infrastructure rather than a mainstream enterprise product.

Key facts
  • CVE ID: CVE-2026-20320
  • Product: Cisco BroadWorks (Application Delivery Platform, Application Server, Profile Server, Xtended Services Platform)
  • Vulnerability type: Out-of-band blind XML External Entity (XXE) injection — CWE-611
  • CVSS 3.1 score: 7.5 (High) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • Cisco advisory: cisco-sa-bworks-xxe-uwUd7CEt, first published August 19, 2026
  • Added to KEV: November 10, 2026
  • Federal remediation due date: November 24, 2026
  • Fixed release: RI.2026.07 (all affected platforms)

What Is Cisco BroadWorks, Anyway?

BroadWorks is Cisco's carrier-grade unified-communications platform. Rather than selling it to individual businesses, Cisco licenses it to telecom service providers — the companies that then resell hosted voice, video conferencing, team messaging, and contact-center features to their own business customers under their own branding. It's the kind of software that sits deep in a provider's back office, handling call routing, provisioning, and billing feeds for potentially millions of subscriber lines across a region or country.

The platform is split into several cooperating server roles, which is why Cisco's advisory names four separate affected components rather than one monolithic product. The Application Server handles call processing and feature logic; the Profile Server and Application Delivery Platform manage subscriber and service configuration; and the Xtended Services Platform extends the system with web and mobile client services. All four share the same vulnerable Open Client Interface code, which is how a single flaw ends up touching the entire product line at once.

Because it's multi-tenant infrastructure serving many downstream business customers at once, a flaw in BroadWorks doesn't just put one company at risk — it can expose the provider's entire subscriber base to downstream consequences if an attacker pivots from the BroadWorks server into connected provisioning or billing systems. That multi-tenant, carrier-of-carriers role is also why this particular KEV addition carries more systemic weight than a single-company bug: one unpatched BroadWorks deployment can sit upstream of dozens of downstream business customers who have no visibility into, or control over, the server's patch status.

How the XXE Flaw Works

The vulnerability sits in BroadWorks' Open Client Interface (OCI), specifically the XML parser used by the OCI-Provisioning (OCI-P) service. According to Cisco's advisory, the parser has external entity resolution enabled by default — a classic setup for an XXE bug. XML parsers that honor external entity references will, when they encounter a specially crafted tag inside an XML document, go fetch or read whatever that tag points to, whether that's a local file path or a network resource.

An attacker doesn't need any credentials or prior access to the BroadWorks environment. They simply submit a crafted XML message to the OCI-P service over the network, and the parser processes the embedded external entity reference as if it were legitimate. Cisco and the National Vulnerability Database both classify this as out-of-band blind XXE: the attacker doesn't get the stolen file contents echoed straight back to them in a visible response. Instead, the exploit is built to exfiltrate data indirectly — for instance, by having the parser reach out to a server the attacker controls, encoding file contents into that outbound request.

The practical result, per Cisco and the NVD entry for CVE-2026-20320, is that a remote, unauthenticated attacker can read arbitrary files from the underlying filesystem with the privileges of the BroadWorks process. That's why the CVSS vector shows a High confidentiality impact (C:H) but no integrity or availability impact (I:N/A:N) — this bug is about reading data, not modifying it or crashing the service. Still, a 7.5 base score for an unauthenticated, network-reachable, low-complexity bug is nothing to shrug off, especially given what kind of files a provisioning server tends to have lying around: database connection strings, API credentials, TLS certificate material, and internal configuration that can be used to move further into the network.

Why XML External Entity Bugs Are a Recurring Headache

XXE flaws, tracked generically under CWE-611, have been a known class of weakness in XML processing for well over a decade, yet they keep showing up in enterprise software because many XML parsing libraries ship with external entity resolution turned on by default. A developer has to explicitly disable that behavior; if they don't, any code path that parses attacker-supplied XML inherits the weakness automatically. That's effectively what happened here — Cisco's advisory attributes the root cause directly to the OCI parser allowing external entity resolution "by default."

The "blind" and "out-of-band" qualifiers in this advisory's title matter for defenders trying to detect exploitation. In a simple XXE attack, a vulnerable parser might reflect the contents of a stolen file straight back in its response, which is comparatively easy to notice in application logs. A blind, out-of-band variant is stealthier: the parser doesn't return file contents in its own response at all. Instead, the malicious XML defines an external entity that points to a server the attacker controls, and the parser's attempt to resolve that entity — often by making an outbound DNS lookup or HTTP request carrying the stolen data encoded in the request itself — is how the data actually leaves the network. That makes outbound traffic monitoring, not inbound request inspection alone, an important part of catching this kind of abuse.

Who's Actually at Risk Here

This is not a consumer-facing bug. The people who need to act are telecom and managed-service operators that run BroadWorks Application Delivery Platform, Application Server, Profile Server, or Xtended Services Platform in their own infrastructure — typically regional and national carriers, cable operators, and UCaaS resellers. If your organization simply subscribes to a hosted phone or video service that happens to be built on BroadWorks behind the scenes, there's no software for you to patch yourself; the fix has to come from your provider.

That said, it's reasonable for business customers of any carrier-hosted voice/UC service to ask their provider, in light of this disclosure, whether their BroadWorks environment has been updated to a fixed release. Telecommunications is also one of the sectors CISA treats as critical infrastructure, which is part of why a flaw in carrier-grade signaling and provisioning software draws a federal KEV listing even though it never touches a consumer's device directly. The exposure here runs through the supply chain: a compromised provisioning server can affect every downstream business relying on that carrier's hosted voice platform, without any of those businesses doing anything wrong themselves.

Affected Products and Fixed Releases

Cisco says the flaw affects BroadWorks regardless of device configuration, across four components. There's no workaround — the only fix is upgrading to release RI.2026.07 or later.

BroadWorks ComponentVulnerable VersionsFixed Release
Application Delivery PlatformEarlier than RI.2026.07RI.2026.07
Application ServerEarlier than RI.2026.07RI.2026.07
Profile ServerEarlier than RI.2026.07RI.2026.07
Xtended Services PlatformEarlier than RI.2026.07RI.2026.07

Cisco credits security researcher Sandesh M Gawai with reporting the issue, which is tracked internally under Cisco bug ID CSCwv48590.

Exploitation Status: What We Actually Know

CISA's KEV catalog only lists vulnerabilities the agency has evidence are being exploited in the wild, and its entry for CVE-2026-20320 sets a federal remediation deadline on that basis. Cisco's own advisory, though, has shifted its language over successive revisions. According to the advisory's revision history, an earlier version described known active exploitation, while the current version (1.2, published November 13, 2026) walks that back, stating Cisco has no direct evidence of active exploitation.

That discrepancy is worth flagging rather than glossing over: it means the precise exploitation picture is murkier than a single confident sentence would suggest. What's consistent across every source is the underlying flaw itself, its CVSS 7.5 severity, and CISA's decision to treat it as a KEV-list priority with a firm federal deadline. Organizations running BroadWorks should treat the KEV listing as the operative signal and patch on that timeline regardless of how the exploitation narrative continues to be refined.

The Federal Deadline and Required Actions

Per the KEV catalog entry, CISA's required action for CVE-2026-20320 is to apply Cisco's mitigations, follow the agency's Binding Operational Directive 26-04 guidance and forensic triage requirements, or discontinue use of the product if mitigations aren't available, with each agency assessing its own internet exposure. The due date is November 24, 2026 — two weeks after the catalog addition.

BOD compliance is mandatory only for federal civilian executive branch agencies, but CISA has consistently recommended that state, local, and private-sector organizations adopt KEV due dates as a best-practice patching prioritization signal, since inclusion in the catalog is itself an indicator that a flaw is attractive to attackers.

This is the latest in a steady run of KEV additions CISA has made this month; it follows, for example, the agency's addition of a UnrealIRCd flaw with a November 16 remediation deadline and an earlier OpenSSH vulnerability added to the same catalog.

What to Do Now

For any organization operating Cisco BroadWorks:

  • Identify your version. Check the release version of every BroadWorks Application Delivery Platform, Application Server, Profile Server, and Xtended Services Platform instance against RI.2026.07.
  • Upgrade. There is no workaround or configuration mitigation for this flaw — Cisco's advisory is explicit that the only fix is upgrading to RI.2026.07 or later.
  • Restrict network exposure to OCI-P. Since the flaw is reachable over the network without authentication, limit which hosts can reach the OCI-Provisioning interface while patching is in progress, consistent with Cisco's general guidance to avoid exposing OCI services to untrusted networks.
  • Watch for outbound anomalies. Because exploitation of this class of bug relies on out-of-band callbacks, unusual outbound DNS or HTTP requests originating from BroadWorks servers toward unfamiliar external hosts are worth investigating.
  • Review BOD 26-04 triage steps if your organization is a federal agency subject to CISA directives, and document remediation ahead of the November 24 deadline.
  • Rotate exposed secrets after patching. Because the flaw's impact is confidentiality-only file disclosure, any credentials, API keys, or certificate material that could plausibly have been reachable from the BroadWorks process should be rotated as a precaution once the server is confirmed to have been vulnerable, even without firm proof a specific file was read.
  • Check vendor-management chains. Managed service providers and resellers that operate BroadWorks on behalf of smaller carriers should confirm with their own upstream vendor that the RI.2026.07 upgrade path has actually been applied, rather than assuming it has.

Security teams can track the official record for this flaw through its CVE.org record and the CWE-611 weakness definition maintained by MITRE, which explains the broader class of XXE issues this bug belongs to. For context on how CISA evaluates and prioritizes vulnerabilities for the KEV list generally, see the Apache mod_http2 critical RCE disclosure Pandromeda covered earlier this year, which followed a similar vendor-advisory-to-KEV pipeline.

What's Next

Expect Cisco to continue refining its advisory as more is learned about exploitation; the jump from "known active exploitation" to "no direct evidence" between revisions 1.1 and 1.2 suggests the company is still working through confirmation. For BroadWorks operators, the practical timeline doesn't change: CISA's November 24 federal deadline stands regardless of how that detail gets resolved, and every organization running the affected platforms should treat the upgrade to RI.2026.07 as urgent rather than routine patch-cycle maintenance, given the flaw requires no authentication and is reachable over the network.

Pandromeda will update this story if Cisco or CISA publish further detail on exploitation activity or if additional affected components come to light.

Frequently asked questions

What is CVE-2026-20320?

CVE-2026-20320 is a high-severity (CVSS 7.5) XML External Entity (XXE) injection vulnerability in the Open Client Interface OCI-P XML parser used by Cisco BroadWorks. It lets an unauthenticated, remote attacker send crafted XML to read sensitive files from the server's filesystem.

Which Cisco BroadWorks versions are affected?

All versions of BroadWorks Application Delivery Platform, Application Server, Profile Server, and Xtended Services Platform prior to release RI.2026.07 are affected, according to Cisco's advisory cisco-sa-bworks-xxe-uwUd7CEt.

What should BroadWorks operators do?

Upgrade all affected components to RI.2026.07 or later. Cisco states there is no workaround, so patching is the only fix. Operators should also restrict network access to the OCI-P service and monitor for unusual outbound traffic in the meantime.

Why did CISA add this to the Known Exploited Vulnerabilities catalog?

CISA added CVE-2026-20320 to its KEV catalog on November 10, 2026, setting a federal civilian agency remediation due date of November 24, 2026, because the agency has evidence tied to active exploitation that meets its KEV inclusion criteria.

Does this vulnerability affect home internet or phone customers directly?

No. BroadWorks is backend carrier infrastructure used by telecom and service providers to deliver hosted voice and unified-communications services; there is no end-user software for consumers to patch. Any fix must come from the provider operating BroadWorks.

Has Cisco confirmed active exploitation of this flaw?

The picture is mixed. An earlier revision of Cisco's advisory described known active exploitation, but the current revision (1.2, published November 13, 2026) states Cisco has no direct evidence of active exploitation. The KEV listing and its deadline stand regardless.

Sources

More on Cisco BroadWorks →Cisco BroadWorksCVE-2026-20320CISA KEV CatalogXXE VulnerabilityVoIP SecurityTelecom Security
Sana Qureshi
Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Security & Privacy

See all