As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Catalyst SD-WAN 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-20313 are related to Improper link resolution before file access issues that are grouped under the Common Weakness Enumeration (CWE) CWE-1284.
CVE-2026-20313
Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-08-05. a secondary CVSS source baseline 7.7; 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.7
- EG Score
- 7.7(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity77% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 5, 2026
Last Modified
August 14, 2026
Advisory Details (1)
Auto-updated Aug 5, 2026Cisco Catalyst SD-WAN Software Security Hardening Release: August 2026
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-hardening-sdwan-faLcR3KVendor Advisories for CVE-2026-20313(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 29× in last 7d / 64× 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 18:09 UTCGHSA enrichment
- 2026-08-20 06:30 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 06:25 UTCGHSA enrichment
- 2026-08-18 18:48 UTCEG score recompute
- 2026-08-18 18:48 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 07:10 UTCGHSA enrichment
- 2026-08-17 19:30 UTCEG score recompute
- 2026-08-17 19:30 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 07:28 UTCGHSA enrichment
- 2026-08-16 19:51 UTCEG score recompute
- 2026-08-16 19:51 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:13 UTCEG score recompute
- 2026-08-16 08:13 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:36 UTCGHSA enrichment
- 2026-08-15 08:58 UTCEG score recompute
- 2026-08-15 08:58 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:20 UTCGHSA enrichment
Show 39 moreShow fewer
- 2026-08-14 10:04 UTCGHSA enrichment
- 2026-08-13 22:26 UTCEG score recompute
- 2026-08-13 22:26 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 10:49 UTCGHSA enrichment
- 2026-08-12 23:11 UTCEG score recompute
- 2026-08-12 23:11 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 11:34 UTCGHSA enrichment
- 2026-08-11 23:56 UTCEG score recompute
- 2026-08-11 23:56 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 12:19 UTCGHSA enrichment
- 2026-08-11 00:42 UTCEG score recompute
- 2026-08-11 00:42 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 13:04 UTCGHSA enrichment
- 2026-08-10 01:27 UTCGHSA enrichment
- 2026-08-09 13:49 UTCEG score recompute
- 2026-08-09 13:49 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 02:12 UTCEG score recompute
- 2026-08-09 02:12 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 14:35 UTCGHSA enrichment
- 2026-08-08 02:57 UTCEG score recompute
- 2026-08-08 02:57 UTCGHSA enrichment
- 2026-08-07 15:19 UTCGHSA enrichment
- 2026-08-07 03:42 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 06:07 UTCEG score recompute
- 2026-08-06 06:07 UTCGHSA enrichment
- 2026-08-05 18:30 UTCEG score recompute
- 2026-08-05 17:56 UTCEG score recompute
- 2026-08-05 17:29 UTCEG score recompute
- 2026-08-05 16:51 UTCEG score recompute
- 2026-08-05 16:50 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-1284
- CVE-2022-20699EG 10.0 KEVEPSS p99CRITICAL
- CVE-2021-21960EG 10.0CRITICAL
- CVE-2021-21951EG 10.0CRITICAL
- CVE-2021-21950EG 10.0CRITICAL
- CVE-2022-25727EG 9.8CRITICAL
- CVE-2022-36938EG 9.8CRITICAL
- CVE-2022-20385EG 9.8CRITICAL
- CVE-2022-37134EG 9.8EPSS p97CRITICAL
- CVE-2021-43267EG 9.8EPSS p99CRITICAL
- CVE-2021-31556EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-20313?
When was CVE-2026-20313 disclosed?
Is CVE-2026-20313 actively exploited?
What is the CVSS score of CVE-2026-20313?
How do I remediate CVE-2026-20313?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-20313
Is Your Infrastructure Affected by CVE-2026-20313?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.