CVE-2026-81378

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. the CNA's CVSS baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 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.

Interpretation conflict in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

CVSS v3
8.2
EG Score
8.2(high)
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-81378

Vendor Advisories for CVE-2026-81378(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 50× in last 7d / 88× 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-19 10:19 UTCVendor advisory
  2. 2026-09-19 10:19 UTCGHSA enrichment
  3. 2026-09-18 21:07 UTCEG score recompute
  4. 2026-09-18 21:07 UTCVendor advisory
  5. 2026-09-18 21:07 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 14:13 UTCVendor advisory
  8. 2026-09-18 14:13 UTCGHSA enrichment
  9. 2026-09-18 12:23 UTCVendor advisory
  10. 2026-09-18 12:23 UTCGHSA enrichment
  11. 2026-09-17 23:07 UTCVendor advisory
  12. 2026-09-17 23:07 UTCGHSA enrichment
  13. 2026-09-17 19:55 UTCEG score recompute
  14. 2026-09-17 19:55 UTCVendor advisory
  15. 2026-09-17 19:55 UTCGHSA enrichment
  16. 2026-09-17 11:27 UTCVendor advisory
  17. 2026-09-17 11:26 UTCGHSA enrichment
  18. 2026-09-16 22:12 UTCEG score recompute
  19. 2026-09-16 22:12 UTCVendor advisory
  20. 2026-09-16 22:12 UTCGHSA enrichment
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 12:00 UTCEG score recompute
  23. 2026-09-16 12:00 UTCVendor advisory
  24. 2026-09-16 12:00 UTCGHSA enrichment
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 63 more
  1. 2026-09-15 22:47 UTCVendor advisory
  2. 2026-09-15 22:47 UTCGHSA enrichment
  3. 2026-09-15 18:00 UTCVendor advisory
  4. 2026-09-15 18:00 UTCGHSA enrichment
  5. 2026-09-15 12:10 UTCEG score recompute
  6. 2026-09-15 12:10 UTCVendor advisory
  7. 2026-09-15 12:10 UTCGHSA enrichment
  8. 2026-09-15 03:12 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-14 22:58 UTCVendor advisory
  11. 2026-09-14 22:58 UTCGHSA enrichment
  12. 2026-09-14 17:50 UTCVendor advisory
  13. 2026-09-14 17:50 UTCGHSA enrichment
  14. 2026-09-14 17:05 UTCVendor advisory
  15. 2026-09-14 17:05 UTCGHSA enrichment
  16. 2026-09-14 03:52 UTCEG score recompute
  17. 2026-09-14 03:52 UTCVendor advisory
  18. 2026-09-14 03:52 UTCGHSA enrichment
  19. 2026-09-13 14:40 UTCVendor advisory
  20. 2026-09-13 14:40 UTCGHSA enrichment
  21. 2026-09-13 01:25 UTCEG score recompute
  22. 2026-09-13 01:25 UTCVendor advisory
  23. 2026-09-13 01:25 UTCGHSA enrichment
  24. 2026-09-12 12:12 UTCVendor advisory
  25. 2026-09-12 12:12 UTCGHSA enrichment
  26. 2026-09-11 22:59 UTCEG score recompute
  27. 2026-09-11 22:59 UTCVendor advisory
  28. 2026-09-11 22:59 UTCGHSA enrichment
  29. 2026-09-11 21:16 UTCEG score recompute
  30. 2026-09-11 21:16 UTCVendor advisory
  31. 2026-09-11 21:16 UTCGHSA enrichment
  32. 2026-09-11 20:07 UTCVendor advisory
  33. 2026-09-11 20:07 UTCGHSA enrichment
  34. 2026-09-11 17:03 UTCEG score recompute
  35. 2026-09-11 17:03 UTCVendor advisory
  36. 2026-09-11 17:03 UTCGHSA enrichment
  37. 2026-09-11 14:53 UTCEPSS rescore
  38. 2026-09-11 14:53 UTCEPSS rescore
  39. 2026-09-11 12:52 UTCEG score recompute
  40. 2026-09-11 12:52 UTCGHSA enrichment
  41. 2026-09-10 23:38 UTCGHSA enrichment
  42. 2026-09-10 11:36 UTCEG score recompute
  43. 2026-09-10 11:36 UTCGHSA enrichment
  44. 2026-09-09 22:21 UTCGHSA enrichment
  45. 2026-09-09 20:10 UTCEG score recompute
  46. 2026-09-09 20:10 UTCVendor advisory
  47. 2026-09-09 20:10 UTCGHSA enrichment
  48. 2026-09-09 19:31 UTCEG score recompute
  49. 2026-09-09 19:31 UTCVendor advisory
  50. 2026-09-09 19:31 UTCGHSA enrichment
  51. 2026-09-09 18:21 UTCEG score recompute
  52. 2026-09-09 18:21 UTCVendor advisory
  53. 2026-09-09 18:21 UTCGHSA enrichment
  54. 2026-09-09 13:03 UTCVendor advisory
  55. 2026-09-09 13:03 UTCGHSA enrichment
  56. 2026-09-08 23:50 UTCEG score recompute
  57. 2026-09-08 23:50 UTCVendor advisory
  58. 2026-09-08 23:49 UTCGHSA enrichment
  59. 2026-09-08 18:58 UTCEG score recompute
  60. 2026-09-08 18:58 UTCGHSA enrichment
  61. 2026-09-08 17:55 UTCEG score recompute
  62. 2026-09-08 17:55 UTCVendor advisory
  63. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81378?
CVE-2026-81378 is a high vulnerability published on September 8, 2026. Interpretation conflict in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
When was CVE-2026-81378 disclosed?
CVE-2026-81378 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-81378 actively exploited?
CVE-2026-81378 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-81378?
CVE-2026-81378 has a CVSS v4.0 base score of 8.2 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-81378?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81378, 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-81378

Explore →

Is Your Infrastructure Affected by CVE-2026-81378?

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

Start Free Scan →Browse All CVEs