~/f4n6 $ grep -r "Actors exploit Openwave and Cisco BroadWorks flaws to leak config data" ./investigations/ --include="*.md"

Actors exploit Openwave and Cisco BroadWorks flaws to leak config data

Jeff Davies 11 Nov 2026 6 min read

1. Executive summary

CISA added CVE-2026-111793 (CVSS 4.3 MEDIUM, CWE-669) and CVE-2026-20320 (CVSS 7.5 HIGH, CWE-611) to the Known Exploited Vulnerabilities catalog on 2026-11-10, citing evidence of active exploitation. The two flaws affect Openwave Messaging Webtop Media Transcoder and Cisco BroadWorks respectively, and both allow an attacker to read sensitive information including configuration data. CVE-2026-20320 is an unauthenticated, remote XML external entity flaw in Cisco BroadWorks; CVE-2026-111793 is the Openwave-side flaw, and public reporting does not describe its mechanism. For EMEA financial services the exposure is concentrated in communications infrastructure: BroadWorks underpins hosted voice and unified communications, and configuration disclosure from that tier can hand an attacker the internal topology and credentials needed for follow-on access. EPSS records 0% for both CVEs, so the practical driver is the confirmed KEV exploitation state, not predicted exploitation volume.

2. Regulatory framing

Article Trigger (the fact in this item) Practical impact
DORA Art. 28: ICT third-party risk — general principles Both affected products (Cisco BroadWorks, Openwave Messaging Webtop Media Transcoder) are third-party ICT products, and CISA's required action is to apply mitigations per vendor instructions or discontinue use where mitigations are unavailable Clients must confirm whether either product sits in their ICT third-party register, obtain the vendor's mitigation status, and record the exposure decision
DORA Art. 30: key contractual provisions with ICT third-party providers The KEV remediation path depends on vendor-supplied mitigations, which places the obligation on the contract with the communications provider Where BroadWorks or Openwave is delivered through a managed or hosted provider, the contract must give the client the right to mitigation timelines and incident notification for this class of flaw

3. Technical analysis & attack chain

The confirmed sequence, as far as public reporting supports it:

  1. CISA added CVE-2026-111793 and CVE-2026-20320 to the KEV catalog on 2026-11-10, citing evidence of active exploitation.
  2. For CVE-2026-20320, an unauthenticated, remote attacker sends crafted XML that the Cisco BroadWorks parser resolves as an external entity, and reads sensitive configuration information from the affected system.
  3. The result on both CVEs is disclosure of sensitive information, including configuration data.

CVE-2026-20320 is the better documented of the two. NVD records it as CWE-611, improper restriction of XML external entity reference, with a CVSS score of 7.5 HIGH. The CISA KEV entry describes the impact as allowing an unauthenticated, remote attacker to read sensitive configuration information on an affected system. That is a read primitive against the configuration store, not code execution. What an attacker does with the configuration afterwards is not described in public reporting.

CVE-2026-111793 is recorded at CVSS 4.3 MEDIUM with CWE-669, incorrect resource transfer between spheres, and is also in CISA KEV as of 2026-11-10. The primary reporting names Openwave Messaging Webtop Media Transcoder as the affected product and states that the flaw lets attackers leak sensitive information including configuration data. The specific vulnerable component, the request path, and the mechanism are not stated in public reporting. The CWE-669 classification suggests a boundary or resource-sharing weakness rather than an injection flaw, but no source describes the exploitation path, so that reading is an inference and should not be treated as a finding.

Affected and fixed versions are not stated in public reporting for either CVE. The Hacker News headline refers to the flaws being actively exploited "despite available patches", which indicates vendor patches exist, but no source in this set names a fixed release, a patch identifier, or a version boundary. Treat version scoping as an open question to put to the vendors directly.

No actor is named in any source. No initial access vector, persistence mechanism, command-and-control channel, lateral movement, or data volume is described. The exploitation is confirmed by CISA KEV; the campaign behind it is not characterised in public reporting.

4. Mitigation & containment

P1 (within 24 hours)

  • Inventory every instance of Cisco BroadWorks and Openwave Messaging Webtop Media Transcoder in the estate, including instances operated by a hosted or managed communications provider. CISA KEV lists both, and the required action is to apply mitigations in accordance with vendor instructions.
  • Where mitigations are unavailable, CISA's KEV guidance is to discontinue use of the product. For internet-facing BroadWorks, restrict reachability to trusted networks and known partner ranges until the vendor mitigation is applied.
  • Open a case with each vendor for the fixed release covering CVE-2026-20320 and CVE-2026-111793. No fixed version is named in public reporting, so the version boundary must come from the vendor.
  • Treat configuration data held by these systems as potentially disclosed. Rotate credentials, API keys and shared secrets that appear in BroadWorks or Openwave configuration.

P2 (within 72 hours)

  • Review logs on BroadWorks and Openwave systems for XML request bodies containing external entity declarations, and for configuration read activity from unexpected source addresses. The XXE mechanism for CVE-2026-20320 means the request carries a document type definition referencing an external entity.
  • Confirm whether the communications provider has applied the vendor mitigation, and obtain the date it was applied. Where the provider cannot confirm, record the gap against the third-party register.

P3 (within 7 days)

  • Add both CVEs to the vulnerability management exception and reporting record, with the KEV addition date of 2026-11-10 and CISA's due date of 2026-11-24 for CVE-2026-20320.
  • Re-test the configuration disclosure path after patching, using the vendor's own validation guidance where it exists.

5. Indicators of compromise

No indicators of compromise available in the source material.

The sources describe the impact of both flaws (configuration data disclosure) but give no file hashes, network indicators, file paths, or command lines. No behavioural indicators specific to the exploitation are described either; the only observable is the XXE request pattern implied by CWE-611, which is covered in §6 rather than listed here as an indicator.

6. Detection

The sources give no artefact strings from the malicious requests, no file names, and no command lines. The only usable detection surface is the XXE request pattern implied by the CVE-2026-20320 classification, which is a generic technique signature rather than an artefact of this campaign. A rule built on it will match legitimate XML traffic that uses external entities and will not distinguish this exploitation from any other XXE attempt. It is included because the CWE is verified and the exposure is confirmed, with that limitation stated.

title: XML External Entity Declaration in Request Body to BroadWorks or Openwave Endpoint
id: 7c1e4b2a-9f3d-4a86-b5e0-2d8c1f6a9b47
status: experimental
description: Detects request bodies containing an XML external entity declaration, the mechanism recorded for CVE-2026-20320 (CWE-611). Generic XXE signature, not specific to this campaign.
author: Adverse Trace
date: 2026-11-11
references:

  - https://nvd.nist.gov/vuln/detail/CVE-2026-20320
logsource:
  category: webserver
detection:
  keywords:

    - '<!ENTITY'
    - 'SYSTEM'
  condition: keywords
fields:

  - clientip
  - cs-uri-stem
  - cs-method
falsepositives:

  - Legitimate XML integrations that declare external entities
level: medium

CVE assessment

2 referenced CVEs — 2 actively exploited (CISA KEV)

CVE CVSS Exploited EPSS Summary
CVE-2026-20320 7.5 High ⚠ KEV 2026-11-10 0% A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticated, remote attack…
CVE-2026-111793 4.3 Medium ⚠ KEV 2026-11-10 0% Openwave Webtop Media Transcoder does not enforce administrator-defined file type restrictions to restrict the file-types to be…

7. Sources

  • SecurityWeek, "Threat Actors Exploit Openwave, Cisco BroadWorks Vulnerabilities", https://www.securityweek.com/threat-actors-exploit-openwave-cisco-broadworks-vulnerabilities/, 2026-11-11
  • The Hacker News, "Cisco BroadWorks and Openwave Flaws Actively Exploited Despite Available Patches", https://thehackernews.com/2026/11/cisco-broadworks-and-openwave-flaws.html
  • CISA Known Exploited Vulnerabilities catalog entry for CVE-2026-20320, Cisco BroadWorks, https://nvd.nist.gov/vuln/detail/CVE-2026-20320

8. Adverse Trace position

Adverse Trace assesses CVE-2026-20320 at CVSS 7.5 HIGH and CVE-2026-111793 at CVSS 4.3 MEDIUM, both confirmed exploited in the wild by their CISA KEV addition on 2026-11-10, with CISA's due date of 2026-11-24 recorded against CVE-2026-20320. Client impact for EMEA financial services is moderate and concentrated in firms running BroadWorks or Openwave in their communications estate, directly or through a provider: the disclosed configuration data is the kind of material that shortens a later intrusion, and the XXE flaw needs no authentication. The absence of a named actor, of affected and fixed version ranges, and of any described post-exploitation activity means the campaign behind the exploitation is uncharacterised in public reporting, and the "available patches" reference in The Hacker News is single-sourced and gives no version. We will ask Cisco and Openwave for the fixed release covering each CVE, re-issue this advisory when version boundaries are published, and contact clients whose third-party register lists BroadWorks or Openwave as a hosted service to confirm mitigation status before the CISA due date.


Read the original source →

Published via PulseTrace — Adverse Trace threat intelligence.

Post this to LinkedIn
Formatting is converted automatically — headings, bullets, a link back & hashtags. Paste straight in.
J
Jeff Davies