As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Secure Workload engineering team has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-20231 are related to improper neutralization of special elements issues that are grouped under the Common Weakness Enumeration (CWE) CWE-74.
CVE-2026-20231
Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-19. a secondary CVSS source baseline 9.9; 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
- 9.9
- EG Score
- 9.9(high)
- EG Risk
- 45(Track)EG Risk 45/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 computedSeverity99% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 20, 2026Cisco Secure Workload Software Security Hardening Release: August 2026
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-csw1-shSvndWPVendor Advisories for CVE-2026-20231(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 15× in last 7d / 15× 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-20 04:19 UTCEG score recompute
- 2026-08-20 04:19 UTCGHSA enrichment
- 2026-08-20 04:08 UTCEG score recompute
- 2026-08-20 04:08 UTCGHSA enrichment
- 2026-08-20 03:39 UTCGHSA enrichment
- 2026-08-20 00:01 UTCGHSA enrichment
- 2026-08-19 20:22 UTCEG score recompute
- 2026-08-19 20:22 UTCGHSA enrichment
- 2026-08-19 19:20 UTCEG score recompute
- 2026-08-19 19:20 UTCGHSA enrichment
- 2026-08-19 18:38 UTCEG score recompute
- 2026-08-19 18:38 UTCGHSA enrichment
- 2026-08-19 17:23 UTCEG score recompute
- 2026-08-19 16:22 UTCEG score recompute
- 2026-08-19 16:22 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-74
- CVE-2014-8423EG 10.0EPSS p99HIGH
- CVE-2015-10062NVD 5.5EG 9.8CRITICAL
- CVE-2015-10027NVD 5.5EG 9.8CRITICAL
- CVE-2016-15007NVD 5.5EG 9.8CRITICAL
- CVE-2016-15004NVD 7.3EG 9.8CRITICAL
- CVE-2013-4144EG 9.8CRITICAL
- CVE-2013-7487EG 9.8CRITICAL
- CVE-2014-4678EG 9.8EPSS p92CRITICAL
- CVE-2014-4967EG 9.8CRITICAL
- CVE-2014-4966EG 9.8CRITICAL
Frequently asked(4)
What is CVE-2026-20231?
When was CVE-2026-20231 disclosed?
What is the CVSS score of CVE-2026-20231?
How do I remediate CVE-2026-20231?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-20231
Is Your Infrastructure Affected by CVE-2026-20231?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.