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.
CVE-2026-20320
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-08-19. a secondary CVSS source baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 19, 2026
Advisory Details (1)
Auto-updated Aug 19, 2026Cisco BroadWorks Out-of-Band Blind XML External Entity Injection Vulnerability
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-bworks-xxe-uwUd7CEtVendor Advisories for CVE-2026-20320(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-19 20:22 UTCEG score recompute
- 2026-08-19 20:22 UTCGHSA enrichment
- 2026-08-19 19:18 UTCEG score recompute
- 2026-08-19 19:18 UTCGHSA enrichment
- 2026-08-19 17:23 UTCEG score recompute
- 2026-08-19 16:52 UTCEG score recompute
- 2026-08-19 16:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-611
- CVE-2015-9280EG 10.0CRITICAL
- CVE-2015-10082NVD 5.5EG 9.8CRITICAL
- CVE-2015-8031EG 9.8CRITICAL
- CVE-2014-2052EG 9.8CRITICAL
- CVE-2013-4334EG 9.8CRITICAL
- CVE-2015-3907EG 9.8CRITICAL
- CVE-2014-3990EG 9.8EPSS p93CRITICAL
- CVE-2014-3244EG 9.8EPSS p92CRITICAL
- CVE-2014-3005EG 9.8EPSS p92CRITICAL
- CVE-2014-3630EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-20320?
When was CVE-2026-20320 disclosed?
What is the CVSS score of CVE-2026-20320?
How do I remediate CVE-2026-20320?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-20320
Is Your Infrastructure Affected by CVE-2026-20320?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.