CISA Adds Cisco BroadWorks CVE-2026-20320 to Exploited Vulnerabilities List: What to Patch
Advertisement
CISA's decision means the bug is being exploited in real attacks, not just theoretical. Cisco disclosed the issue on August 19, 2026, so organizations that have not applied the August update have been exposed for almost three months.
Cisco BroadWorks is Cisco's platform for cloud and carrier voice, messaging and collaboration services, so affected organizations include service providers and enterprises that run it. If your company relies on a provider that uses BroadWorks, ask that provider about patch status. Read the CISA Known Exploited Vulnerabilities Catalog entry and follow NIST Cybersecurity Framework practices for vulnerability response.
What Happened
CISA added the flaw to its KEV catalog on November 10, 2026, after Cisco disclosed and patched it in August. The vulnerability sits in the OCI-P provisioning interface. CISA added CVE-2026-20320 to its KEV catalog on November 10, 2026, according to BleepingComputer. The flaw is an XML external entity (XXE) weakness in the Open Client Interface (OCI) XML parser of Cisco BroadWorks.
An unauthenticated remote attacker can send a crafted XML message to the OCI-P provisioning service and read sensitive files, such as configuration data, with the privileges of the BroadWorks user. BleepingComputer reports that external entity resolution is enabled by default. The Rescana analysis lists the issue as CWE-611, rates it High with a CVSS 3.1 score of 7.5 and notes that Cisco's advisory is dated August 19, 2026.
- Disclosure: August 19, 2026 (Cisco advisory cisco-sa-bworks-xxe-uwUd7CEt).
- KEV listing: November 10, 2026.
- Federal remediation deadline: November 24, 2026.
- Fixed release: RI.2026.07.
- Workaround: none, per Rescana's review of the advisory; Cisco recommends upgrading.
CISA did not share details on who is exploiting the flaw or how widely. Treat claims about specific attackers as unconfirmed unless Cisco or CISA publishes them.
Why It Matters
A KEV listing is the strongest public signal that a vulnerability is being used in attacks. Although the formal deadline applies to US federal civilian agencies, CISA encourages all organizations to prioritize KEV entries because attackers rarely limit themselves to government targets.
The flaw also exposes configuration and credential material. File-read bugs can reveal keys, certificates and settings that help attackers move further, so a successful read can lead to a larger incident even if no code runs on the server.
What It Means for B2B SaaS Buyers and IT Teams
If you operate BroadWorks yourself, you must patch. If you buy voice or collaboration services from a provider that does, you depend on their patching, and your contract and security questionnaire should reflect that dependency.
- Telecom and UCaaS providers: confirm your BroadWorks release and exposure of the OCI-P service.
- Enterprises with hosted voice: ask the provider for patch status and incident history.
- Security teams: add CVE-2026-20320 to your vulnerability tracker with a KEV flag and a due date.
- Procurement: require breach and vulnerability notification terms in vendor agreements.
What to Do Now: Checklist
Upgrade to RI.2026.07 or later, restrict network access to the OCI-P service, review logs for unusual XML requests and rotate any credentials or keys that may have been exposed. Prioritize internet-facing systems first.
- Identify every BroadWorks instance and its release level.
- Apply Cisco's fix and confirm the Application Delivery Platform components are on the fixed release.
- Limit OCI-P access to trusted management networks.
- Search logs for unexpected requests to the provisioning interface.
- Rotate certificates, keys and service credentials if you suspect access.
- Document the change for audit and customer reporting.
Use the Cisco advisory as the authoritative source for fixed versions and any updates.
Related Tools on SaaSPodium
Security teams that must track and close exploited flaws faster can use dedicated software for scanning and patching. Teams that need to find and fix known exploited flaws faster can compare tools in our vulnerability management software and patch management software categories. For background reading, see automated patch management tools compared and the network vulnerability scanner comparison.
Frequently Asked Questions
Is CVE-2026-20320 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on November 10, 2026, which indicates evidence of active exploitation. CISA has not published details on the attackers or the scale of attacks.
How do I fix CVE-2026-20320?
Upgrade Cisco BroadWorks to release RI.2026.07 or later. Cisco lists no workaround, so restrict access to the OCI-P service as a stopgap and review logs for suspicious XML requests.
Does the November 24 deadline apply to private companies?
The binding deadline applies to US federal civilian agencies. CISA urges all organizations to treat KEV entries as priorities, so private companies should patch on the same schedule where possible.
Advertisement