As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco IOS XE Software engineering team has conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-20268 are related to issues with improper restriction of operations within the bounds of a memory buffer that are grouped under the Common Weakness Enumeration (CWE) Pillar CWE-119.
CVE-2026-20268
Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 8.6; 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
- 8.6
- EG Score
- 8.6(high)
- EG Risk
- 54(Track)EG Risk 54/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 computedSeverity86% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 19%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 14, 2026
Advisory Details (1)
Auto-updated Aug 5, 2026Cisco IOS XE Software Security Hardening Release: August 2026
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-iosxe-V8NMuMZJVendor Advisories for CVE-2026-20268(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 28× in last 7d / 62× 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 20:45 UTCGHSA enrichment
- 2026-08-20 07:48 UTCGHSA enrichment
- 2026-08-19 18:52 UTCEG score recompute
- 2026-08-19 18:52 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 04:55 UTCGHSA enrichment
- 2026-08-18 15:58 UTCEG score recompute
- 2026-08-18 15:58 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 02:59 UTCGHSA enrichment
- 2026-08-17 14:02 UTCEG score recompute
- 2026-08-17 14:02 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:06 UTCEG score recompute
- 2026-08-17 01:06 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:10 UTCEG score recompute
- 2026-08-16 12:10 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 23:14 UTCGHSA enrichment
- 2026-08-15 10:17 UTCEG score recompute
- 2026-08-15 10:17 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:20 UTCGHSA enrichment
- 2026-08-14 17:55 UTCGHSA enrichment
Show 37 moreShow fewer
- 2026-08-14 04:59 UTCEG score recompute
- 2026-08-14 04:59 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 16:03 UTCGHSA enrichment
- 2026-08-13 03:00 UTCGHSA enrichment
- 2026-08-12 14:04 UTCEG score recompute
- 2026-08-12 14:04 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 01:27 UTCEG score recompute
- 2026-08-12 01:27 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 12:31 UTCEG score recompute
- 2026-08-11 12:31 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 23:35 UTCGHSA enrichment
- 2026-08-10 10:39 UTCGHSA enrichment
- 2026-08-09 21:42 UTCEG score recompute
- 2026-08-09 21:42 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 08:46 UTCGHSA enrichment
- 2026-08-08 19:50 UTCEG score recompute
- 2026-08-08 19:50 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 06:54 UTCGHSA enrichment
- 2026-08-07 17:57 UTCEG score recompute
- 2026-08-07 17:57 UTCGHSA enrichment
- 2026-08-07 05:01 UTCGHSA enrichment
- 2026-08-06 16:05 UTCEG score recompute
- 2026-08-06 16:05 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 07:28 UTCGHSA enrichment
- 2026-08-05 18:31 UTCEG score recompute
- 2026-08-05 18:31 UTCGHSA enrichment
- 2026-08-05 17:57 UTCEG score recompute
- 2026-08-05 17:29 UTCEG score recompute
- 2026-08-05 16:52 UTCEG score recompute
- 2026-08-05 16:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-119
- CVE-2003-0819EG 10.0EPSS p99HIGH
- CVE-2003-0903EG 10.0EPSS p98HIGH
- CVE-2003-1339EG 10.0EPSS p99HIGH
- CVE-2003-0095EG 10.0EPSS p96HIGH
- CVE-2002-2227EG 10.0HIGH
- CVE-2002-2248EG 10.0EPSS p92HIGH
- CVE-2002-2250EG 10.0EPSS p94HIGH
- CVE-2002-2251EG 10.0EPSS p93HIGH
- CVE-2002-2253EG 10.0EPSS p93HIGH
- CVE-2002-2257EG 10.0EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-20268?
When was CVE-2026-20268 disclosed?
Is CVE-2026-20268 actively exploited?
What is the CVSS score of CVE-2026-20268?
How do I remediate CVE-2026-20268?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-20268
Is Your Infrastructure Affected by CVE-2026-20268?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.