On Nov. 10, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added a Cisco BroadWorks vulnerability to its Known Exploited Vulnerabilities (KEV) catalog. The flaw, tracked as CVE-2026-20320, was not new. Cisco had published a fix 83 days earlier, on Aug. 19. A KEV listing means CISA has evidence that attackers are now using the bug. Federal civilian agencies have until Nov. 24 to deal with it.

BroadWorks is Cisco's platform for hosted voice and unified communications. Service providers use it to run cloud phone systems for business customers. Most small businesses and many IT teams never touch a BroadWorks server themselves, but the phone service they pay for may run on one. Organizations that run BroadWorks in-house, or that resell or manage voice services built on it, need to check their release versions this week.

What is the bug?

According to Cisco's advisory (cisco-sa-bworks-xxe-uwUd7CEt, bug ID CSCwv48590), the problem is in the XML parser that handles the Open Client Interface, or OCI. The advisory says an attacker would send a crafted XML message to the Open Client Interface - Provisioning (OCI-P) service, the provisioning interface that BroadWorks exposes so other systems can manage it by sending XML messages.

The flaw is an XML External Entity (XXE) injection, classified as CWE-611. XML allows a document to declare "external entities," which are references that tell the parser to fetch content from somewhere else, such as a local file or a remote address. A parser that resolves those references for untrusted input can be tricked into reading files it should never touch. Cisco says external entity resolution was allowed by default in the affected OCI parser.

Cisco calls this an "out-of-band blind" XXE. "Blind" generally means the stolen file contents do not come back in the server's normal response. "Out-of-band" generally means the attacker gets the data out by another route, typically by making the vulnerable server send it to infrastructure the attacker controls. To the defender, the practical result is the same as with any XXE file read: a remote attacker who can reach the OCI-P service can read files on the server.

Cisco's advisory says an attacker would need:

  • No authentication. No login is required. The CVSS vector lists privileges required as none (PR:N).
  • No user interaction. No one has to click anything (UI:N).
  • Network access to the OCI-P service. The attacker sends crafted XML to it (AV:N, AC:L).

The attacker can view files on the filesystem with the privileges of the BroadWorks user. Cisco rates the flaw High, with a CVSS 3.1 score of 7.5, and the confidentiality impact is rated High. CISA's KEV description says the flaw lets an attacker read sensitive configuration information. The advisory does not list specific files, so we won't guess which ones.

Which products are affected?

Cisco lists four BroadWorks components as vulnerable when they run a release earlier than RI.2026.07:

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

RI.2026.07 is the first fixed release. Cisco says there are no workarounds, so upgrading is the only remedy the vendor offers.

Why the KEV listing matters now

When Cisco published the advisory in August, it said its Product Security Incident Response Team (PSIRT) was not aware of any public announcements or malicious use of the vulnerability, and it gave no workarounds. For many organizations, a 7.5-rated bug on a voice platform with no reported attacks ends up in the regular patch cycle rather than being handled as an emergency. The KEV listing should change that.

The NVD record for CVE-2026-20320, last modified Nov. 11, now includes CISA's own assessment, dated Nov. 10. CISA uses SSVC (Stakeholder-Specific Vulnerability Categorization), a decision framework for ranking vulnerabilities. Its SSVC entry for this bug records three findings:

  • Exploitation: active. CISA has seen the bug used against real targets.
  • Automatable: yes. Attacks can be scripted and scaled, so an attacker can hit many exposed systems quickly instead of working on one target at a time.
  • Technical impact: partial. In SSVC terms, the attacker gets limited control over the system, which fits a file-read flaw.

In the sources we reviewed, neither CISA nor Cisco names the attackers, says how many organizations are affected or describes what was taken. The KEV feed lists known ransomware campaign use as "Unknown." That means CISA has not tied the bug to ransomware. It does not mean ransomware has been ruled out.

The KEV entry's required action tells agencies to apply mitigations in accordance with vendor instructions and the guidance in Binding Operational Directive (BOD) 26-04, or to discontinue use of the product if mitigations are unavailable. The due date is Nov. 24, two weeks after the listing. The directive formally binds only federal civilian agencies, but many private-sector security teams use the KEV catalog as a priority list, and it is a reasonable one to follow.

A busy week for KEV

The BroadWorks entry was not the only addition. The same KEV feed shows that on Nov. 9, CISA added CVE-2026-123218, an incorrect authorization vulnerability in IBM Aspera Faspex. CISA gave agencies only until Nov. 12 to address that one, a three-day window, compared with two weeks for BroadWorks. That entry also has the feed's forensic triage field set to "Yes," while the BroadWorks entry has it set to "No." We have not reviewed IBM's own advisory for the Aspera flaw. Faspex administrators should go straight to IBM's guidance.

What It Means for Defenders

Who is affected: Anyone running BroadWorks Application Delivery Platform, Application Server, Profile Server or Xtended Services Platform on a release earlier than RI.2026.07. That likely means telecom carriers, hosted-voice providers, managed service providers and large enterprises that run their own BroadWorks deployments. If you only buy phone service from a provider, the fix is the provider's job. It is still worth asking them directly whether they have patched CVE-2026-20320.

What to patch: Upgrade every affected component to RI.2026.07 or later. Cisco offers no workaround. If you can't upgrade before the Nov. 24 KEV deadline, the KEV required action says to discontinue use of the product if mitigations are unavailable, and here Cisco says none exist. Agencies should follow BOD 26-04 either way.

What to check:

  • Exposure. Find every system that can reach the OCI-P provisioning interface. This is a provisioning interface for other systems to use, so review whether it really needs to be reachable from wide networks or the internet. Narrowing that reachability is good practice, but it does not replace the patch. Cisco does not offer it as a workaround.
  • Outbound traffic. Out-of-band XXE attacks usually make the victim server connect out to a system the attacker controls. Look for unexpected outbound connections from BroadWorks servers, especially since Aug. 19, and consider limiting outbound traffic from these hosts to known destinations.
  • OCI-P request logs. Review provisioning requests from unfamiliar sources and XML that doesn't match what your normal integrations send.

What to rotate: The bug exposes files the BroadWorks user can read. If you find signs of compromise, or can't rule it out on a server that was exposed while unpatched, treat any credentials, keys or secrets stored in files readable by that account as possibly stolen and rotate them. The sources don't say which files attackers have gone after. Base this review on what your own deployment stores.

For CMMC and federal contractors: The KEV catalog is an easy, defensible way to set patch priorities. Record the patch date, or your compensating decision, against the Nov. 24 due date in your vulnerability management records so you can show how KEV items were handled relative to CISA's timeline.

And for Faspex shops: The Aspera Faspex KEV entry, CVE-2026-123218, was due Nov. 12. If it isn't handled yet, it is overdue or due today.

Sources