High 7.5In CISA KEVPatch available
CVE-2026-20320
A vulnerability in the Open Client Interface (OCI) XML Parser of Cisco BroadWorks could allow an unauthenticated, remote attacker to read sensitive configuration information on an affected system. This vulnerability exists because XML entries are improperly parsed due to external entity resolution being allowed by default. An attacker could exploit this vulnerability by sending a crafted XML message to the Open Client Interface – Provisioning (OCI-P) service. A successful exploit could allow the attacker to view sensitive files from the filesystem with the privileges of the Cisco BroadWorks user.
How scary is it?
updated 21 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- None known
Public exploit code is out
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- Yes
Attacks seen in the wild2
CISA lists it as exploited in the wild.
- Yes
On CISA's exploited list (since 10 Nov 2026)2
CISA deadline for US federal agencies: 24 Nov 2026.
Scare-o-meter
Drop everything
Attackers are already on it. Patch now.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.2 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
Product names from our AI analysisYou run one of the products named in our analysiscisco:broadworks_application_delivery_platform / cisco:broadworks_application_server / cisco:broadworks_profile_server / cisco:broadworks_xtended_services_platform
We hold no version range from the vendor for this CVE. These product names were written by a language model from the CVE record: check them against the sources.
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA's required action for this KEV entry, due 24 Nov 2026 for US federal agencies.
Source 2
- CVSS
- 7.5Highscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 10 Nov 2026CISA deadline for US federal agencies: 24 Nov 2026
- EPSS
- 1.7%chance of exploitation in the next 30 daystop 23% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 19 Aug 2026analysed here 21 Nov 2026
Do first. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. (CISA's required action for this KEV entry)
Summary
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
Products named in our analysis
- cisco:broadworks_application_delivery_platform
- cisco:broadworks_application_server
- cisco:broadworks_profile_server
- cisco:broadworks_xtended_services_platform
Fix and mitigation
WAF and other mitigations
Can a WAF block it? Partly. The attack is delivered via a crafted XML message in an HTTP request to the Open Client Interface - Provisioning service. The malicious XML contains external entity references, which are unusual and could be detected by a WAF inspecting XML payloads for such patterns. A custom WAF rule can filter crafted XML message with external entity references to the OCI-P service, but attackers can vary the request. No tracked WAF vendor has published a rule for this CVE yet.
What a custom rule would match: crafted XML message with external entity references to the OCI-P service
Also consider: patch · custom WAF rule · disable DTDs in parser
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 10 Nov 2026.
- CISA due date
- 24 Nov 2026, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation active, automatable yes, technical impact partialAssessed by CISA 10 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 19 Aug 2026Published
- 10 Nov 2026Added to CISA KEV (exploited in the wild)82 days (about 3 months) later
- 10 Nov 2026CISA SSVC assessment: exploitation activesame day later
- 13 Nov 2026CVE record last updated4 days later
- 21 Nov 2026Analysed by vulneraibility.com7 days later
- 24 Nov 2026CISA remediation due date (US federal agencies)3 days later
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
| Metric | Value | What it means |
|---|---|---|
| Attack vector | NetworkReachable over the internet or any routable network. | Reachable over the internet or any routable network. |
| Attack complexity | LowRepeatable attack, no special conditions. | Repeatable attack, no special conditions. |
| Privileges required | NoneThe attacker needs no prior access. | The attacker needs no prior access. |
| User interaction | NoneNo victim action needed. | No victim action needed. |
| Scope | UnchangedImpact stays within the vulnerable component. | Impact stays within the vulnerable component. |
| Confidentiality | HighTotal data disclosure possible. | Total data disclosure possible. |
| Integrity | NoneNo unauthorised modification. | No unauthorised modification. |
| Availability | NoneThe service stays up. | The service stays up. |
Common questions
Is CVE-2026-20320 being exploited?
Yes. CVE-2026-20320 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-20320?
CVE-2026-20320 is rated High with a CVSS score of 7.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-20320?
Yes. A fix has been recorded for CVE-2026-20320. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-20320 affect?
CVE-2026-20320 affects cisco:broadworks_application_delivery_platform, cisco:broadworks_application_server, cisco:broadworks_profile_server, cisco:broadworks_xtended_services_platform. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
3 references in the CVE record, grouped by the tags the record gives them.
Advisories (1)
- malbearlabs.com /posts/operation-snowball-inside-an-autonomous-ai-intrusion-campaign
Other links (2)
- sec.cloudapps.cisco.com /security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe-uwUd7CEt
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-20320
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.