All articles

NewsNovember 10, 20264 min read

Cisco BroadWorks, CVE-2026-20320: XXE exploited (CISA KEV)

Cisco BroadWorks: an XXE in the OCI-P XML parser lets a remote attacker read sensitive files without credentials. Exploited, now in the KEV catalog.

The words “Data Loss” in yellow inside a frame of binary code

On 10 November 2026 CISA, the US cybersecurity agency, added CVE-2026-20320 to its Known Exploited Vulnerabilities (KEV) catalog. It is an XML External Entity (XXE) vulnerability in Cisco BroadWorks. Inclusion in the catalog means CISA has evidence of active exploitation. According to the National Vulnerability Database (NVD) entry, the flaw allows a remote, unauthenticated attacker to read sensitive configuration information on an affected system.

The information in this article comes from a single source: the KEV catalog entry and the linked NVD record. The sources do not say who exploited the vulnerability, against which organisations or to what end. The CVE has been public on NVD since 19 August 2026: its addition to KEV comes almost three months later.

How the vulnerability works

According to the description published on NVD, the problem lies in the XML parser of the Open Client Interface (OCI) of Cisco BroadWorks. The parser resolves external entities by default, so XML entries are not parsed correctly.

An attacker can exploit the flaw by sending a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service. A successful attack lets them view sensitive files from the filesystem with the privileges of the Cisco BroadWorks system user.

In an XXE attack the XML document declares an entity that points to an external resource, such as a local file, and the parser includes its content in the processing. The sources do not describe the files read in the observed exploitation or the full attack chain.

Technical details

  • CVE: CVE-2026-20320, published on NVD on 19 August 2026, status “Analyzed”, last modified on 11 November 2026.
  • Weakness: CWE-611 (Improper Restriction of XML External Entity Reference).
  • CVSS 3.1: 7.5, high severity, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, assigned by Cisco’s PSIRT: network attack, low complexity, no privileges and no user interaction required, high impact on confidentiality, no impact on integrity and availability.
  • Affected products according to the NVD configuration:
    • Cisco BroadWorks Application Delivery Platform, versions earlier than RI.2026.07;
    • Cisco BroadWorks Application Server, versions earlier than 2026.0;
    • Cisco BroadWorks Profile Server, versions earlier than 2026.07;
    • Cisco BroadWorks Xtended Services Platform, versions earlier than 2026.07.
  • KEV catalog: added on 10 November 2026; the deadline for US federal agencies to act is 24 November 2026. Use in ransomware campaigns is listed as “unknown”.
  • References: Cisco’s security advisory cisco-sa-bworks-xxe-uwUd7CEt, listed by NVD as the vendor advisory. NVD also lists a third-party analysis by Malbear Labs, titled “Operation Snowball: inside an autonomous AI intrusion campaign” and tagged as an exploit; the sources of this article do not report its content.
  • MITRE ATT&CK: for an OCI-P service reachable from the network, the corresponding technique is T1190 (Exploit Public-Facing Application).

The sources do not report any indicators of compromise.

Impact for European and Italian companies

The flaw does not allow data to be modified or the service to be stopped, but it gives read access to system files, including sensitive configuration information, without the need for an account. Configuration files can contain data an attacker can use for the next steps.

The CVSS score is “high” rather than “critical”, but inclusion in the KEV catalog shows that the vulnerability is already being exploited: priority should be set on that basis, not on the score alone.

For entities in scope of NIS2, including organisations that provide communication services, managing known vulnerabilities and patching promptly are part of the required security measures. The KEV catalog is binding only on US federal agencies, but it is a useful guide for setting priorities in Europe too.

What to do now

  1. Check the versions of the Cisco BroadWorks components in use against those listed: Application Delivery Platform, Application Server, Profile Server and Xtended Services Platform.
  2. Apply the fixes or mitigations in Cisco’s advisory cisco-sa-bworks-xxe-uwUd7CEt. CISA asks for mitigations to be applied according to the vendor’s instructions and, if none are available, for use of the product to be discontinued.
  3. Reduce exposure: CISA urges an assessment of each installation’s internet exposure. Check whether the OCI-P service is reachable from networks that do not need it and restrict access to authorised systems only.
  4. Look for signs of exploitation: in the OCI-P service logs, check for XML messages containing DOCTYPE or ENTITY declarations: external entities are the mechanism an XXE attack relies on.
  5. Review credentials: if a system was left exposed with a vulnerable version, consider changing the passwords and keys found in configuration files readable by the BroadWorks user, because the flaw allows them to be read.
  6. Preserve logs before working on suspicious systems: for federal agencies CISA refers to its own forensic triage requirements, and for companies too the logs are needed to understand what happened.

How ARXDOME helps

ARX Expose shows what can be seen of your company from outside, with open ports, recognised products and known vulnerabilities on public services: a provisioning interface exposed to the internet comes to light. ARX Horizon weighs vulnerabilities against the catalog of exploited ones, updated daily, so a flaw like CVE-2026-20320 rises to the top of the priorities. ARX Sentry collects logs and events from monitored machines, useful for hunting suspicious activity on the servers hosting the platform.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles