On this page (7 sections)

CISA has added CVE-2026-20320, an XML external entity (XXE) vulnerability in Cisco BroadWorks, to its Known Exploited Vulnerabilities (KEV) catalog. The flaw sits in the Open Client Interface (OCI) XML parser and lets an unauthenticated remote attacker read sensitive files from the affected system.

If your organization runs Cisco BroadWorks, or you host or manage it for a telecom or UCaaS customer, treat this as a priority. Details such as affected and fixed versions are not in the public records we reviewed, so the vendor advisory is the document to work from.

What happened

The vulnerability was published on 2026-08-19 and described in the GitHub Advisory Database and the NVD record. On 2026-11-10, according to the CVE data we reviewed, CISA added it to the KEV catalog with a remediation due date of 2026-11-24. KEV inclusion means CISA has evidence of exploitation in the wild.

The research does not say who is exploiting the flaw, how many systems are affected or what was taken. CISA lists ransomware campaign use as unknown. Cisco's own advisory is the primary source: cisco-sa-bworks-xxe-uwUd7CEt.

Technical details in plain terms

XML documents can contain entities, which are placeholders the parser replaces with other content. An external entity points to a resource outside the document, such as a local file. If a parser resolves these by default, an attacker can craft a message that makes the server pull in a file and return or expose its contents. This weakness class is CWE-611.

According to the advisory text, BroadWorks parses XML entries improperly because external entity resolution is allowed by default. An attacker sends a crafted XML message to the Open Client Interface - Provisioning (OCI-P) service and can view sensitive files on the filesystem with the privileges of the BroadWorks user.

The CVSS v3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. In practice: reachable over the network, low complexity, no login and no user interaction, with a high impact on confidentiality only. No integrity or availability impact is scored. The GitHub record shows an EPSS value of 0.385%, but that estimate predates the KEV listing and should not lower your priority.

Who is affected

Organizations running Cisco BroadWorks with the OCI-P service reachable by an attacker are the realistic targets. That includes service providers and enterprises that expose provisioning interfaces to partner networks, management networks or the internet. Because no authentication is required, exposure of the service is the key risk factor.

Configuration files on a telephony platform can hold credentials, internal hostnames and integration details. The sources do not say what was read in observed attacks, but stolen secrets would be a likely follow-on concern, so plan for credential rotation if you find signs of abuse.

How to check your exposure

  • Confirm whether you run BroadWorks at all, including instances managed by a vendor or hosting partner.
  • Find your installed BroadWorks version and compare it with the fixed releases in the Cisco advisory. The public records reviewed here do not list them.
  • Identify which networks can reach the OCI-P service. Check firewall rules, load balancers and any NAT or port forwarding that publishes it.
  • Review application and network logs for unexpected or malformed XML requests to OCI-P, especially from unfamiliar source addresses.
Cisco's advisory is the authority on affected releases and available fixes or mitigations. The sources used for this article do not state them, so do not assume a version is safe without checking.

What to do now

  1. Open the Cisco advisory cisco-sa-bworks-xxe-uwUd7CEt and note the affected releases and the fixed releases or mitigations.
  2. Apply the vendor fix or mitigation as soon as your change process allows. CISA's KEV due date for US federal agencies is 2026-11-24, a useful benchmark for everyone else.
  3. Restrict network access to OCI-P so only known provisioning systems and management hosts can reach it. Do not leave it open to the internet.
  4. Review logs from before the fix for suspicious requests to OCI-P, and keep copies for investigation.
  5. If you see signs of abuse, rotate credentials and secrets stored in BroadWorks configuration files and in systems it integrates with.
  6. Record the system, version and fix date so you can show compliance later.
Caution. Patching or reconfiguring a voice platform can interrupt calls and provisioning. Schedule a maintenance window and follow Cisco's instructions for your deployment.

Detection and monitoring afterwards

Because exploitation reads files rather than changing them, it may leave little trace. Rely on request logging for the OCI-P service, alerts for connections from new source addresses and monitoring of outbound traffic from BroadWorks hosts. Keep an eye on the CISA KEV entry and the Cisco advisory for updates, since details may be revised.

For any public-facing web or management endpoints around your telephony stack, a certificate and DNS monitor can flag unexpected changes, and the free SSL checker gives a quick look at your certificates. These do not detect or block this specific flaw. Reducing what is reachable from the internet remains the most effective control, and the WAF primer explains where filtering helps and where it does not.

If you suspect compromise, follow a structured response such as website hacked: what to do, adapting the steps to your telephony environment.

Timeline

Summary
DateEvent
2026-08-19CVE-2026-20320 published; GitHub advisory GHSA-9w8j-fg77-whw7 added
2026-11-10CISA adds the CVE to the KEV catalog
2026-11-24CISA remediation due date listed in the KEV entry

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-20320 - GitHub Advisory Databasegithub.com
  2. Cisco BroadWorks Improper Restriction of XML External Entity Reference Vulnerability (CVE-2026-20320) is being actively exploitednvd.nist.gov ·
  • Cisco
  • BroadWorks
  • XXE
  • CISA KEV
  • CVE-2026-20320