CVE-2026-81383

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 4 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.4Exploit: None knownExposed: 0

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

Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.

CVSS v3
7.4
EG Score
7.4(high)
EG Risk
34(Track)
EG Risk 34/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
Severity74% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
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-81383

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

Frequently asked(5)

What is CVE-2026-81383?
CVE-2026-81383 is a high vulnerability published on September 8, 2026. Use of incorrectly-resolved name or reference in Visual Studio Code allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-81383 disclosed?
CVE-2026-81383 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-81383 actively exploited?
CVE-2026-81383 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.6% of all scored CVEs.
What is the CVSS score of CVE-2026-81383?
CVE-2026-81383 has a CVSS v4.0 base score of 7.4 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-81383?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81383, 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-81383

Explore →

Is Your Infrastructure Affected by CVE-2026-81383?

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

Start Free Scan →Browse All CVEs