CVE-2026-81379

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:microsoft, epss
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
37(Track)
EG Risk 37/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 computed
Severity82% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81379

Vendor Advisories for CVE-2026-81379(1)

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 33× in last 7d / 54× 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.

  1. 2026-09-18 21:07 UTCEG score recompute
  2. 2026-09-18 21:07 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 14:13 UTCVendor advisory
  5. 2026-09-18 10:01 UTCVendor advisory
  6. 2026-09-17 23:07 UTCVendor advisory
  7. 2026-09-17 20:12 UTCVendor advisory
  8. 2026-09-17 19:55 UTCEG score recompute
  9. 2026-09-17 19:55 UTCVendor advisory
  10. 2026-09-17 09:06 UTCVendor advisory
  11. 2026-09-16 22:12 UTCVendor advisory
  12. 2026-09-16 21:16 UTCEG score recompute
  13. 2026-09-16 21:16 UTCVendor advisory
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 09:42 UTCEG score recompute
  16. 2026-09-16 09:42 UTCVendor advisory
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 22:47 UTCVendor advisory
  19. 2026-09-15 18:00 UTCVendor advisory
  20. 2026-09-15 09:52 UTCEG score recompute
  21. 2026-09-15 09:52 UTCVendor advisory
  22. 2026-09-15 03:12 UTCEPSS rescore
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-14 22:58 UTCVendor advisory
  25. 2026-09-14 17:50 UTCVendor advisory
Show 29 more
  1. 2026-09-14 16:23 UTCVendor advisory
  2. 2026-09-14 05:29 UTCVendor advisory
  3. 2026-09-13 18:35 UTCEG score recompute
  4. 2026-09-13 18:35 UTCVendor advisory
  5. 2026-09-13 07:40 UTCVendor advisory
  6. 2026-09-12 20:47 UTCEG score recompute
  7. 2026-09-12 20:47 UTCVendor advisory
  8. 2026-09-12 09:53 UTCVendor advisory
  9. 2026-09-11 22:59 UTCEG score recompute
  10. 2026-09-11 22:59 UTCVendor advisory
  11. 2026-09-11 21:16 UTCEG score recompute
  12. 2026-09-11 21:16 UTCVendor advisory
  13. 2026-09-11 20:07 UTCVendor advisory
  14. 2026-09-11 17:03 UTCEG score recompute
  15. 2026-09-11 17:03 UTCVendor advisory
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 10:36 UTCEG score recompute
  19. 2026-09-10 23:38 UTCEG score recompute
  20. 2026-09-10 15:26 UTCEG score recompute
  21. 2026-09-10 14:45 UTCEG score recompute
  22. 2026-09-09 20:10 UTCVendor advisory
  23. 2026-09-09 10:44 UTCVendor advisory
  24. 2026-09-08 23:50 UTCEG score recompute
  25. 2026-09-08 23:50 UTCVendor advisory
  26. 2026-09-08 18:58 UTCEG score recompute
  27. 2026-09-08 17:55 UTCEG score recompute
  28. 2026-09-08 17:55 UTCVendor advisory
  29. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81379?
CVE-2026-81379 is a high vulnerability published on September 8, 2026. Not failing securely ('failing open') in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-81379 disclosed?
CVE-2026-81379 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81379 actively exploited?
CVE-2026-81379 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.6% of all scored CVEs.
What is the CVSS score of CVE-2026-81379?
CVE-2026-81379 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-81379?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81379, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81379

Explore →

Is Your Infrastructure Affected by CVE-2026-81379?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.