CVE-2026-81381

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

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

Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.

CVSS v3
7.5
EG Score
7.5(medium)
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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
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-81381

Vendor Advisories for CVE-2026-81381(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 51× in last 7d / 81× 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-20 19:30 UTCVendor advisory
  2. 2026-09-20 19:30 UTCGHSA enrichment
  3. 2026-09-20 08:05 UTCVendor advisory
  4. 2026-09-20 08:05 UTCGHSA enrichment
  5. 2026-09-19 19:56 UTCEG score recompute
  6. 2026-09-19 19:56 UTCVendor advisory
  7. 2026-09-19 19:56 UTCGHSA enrichment
  8. 2026-09-19 08:32 UTCVendor advisory
  9. 2026-09-19 08:32 UTCGHSA enrichment
  10. 2026-09-18 21:07 UTCEG score recompute
  11. 2026-09-18 21:07 UTCVendor advisory
  12. 2026-09-18 21:07 UTCGHSA enrichment
  13. 2026-09-18 19:28 UTCEPSS rescore
  14. 2026-09-18 14:13 UTCVendor advisory
  15. 2026-09-18 14:13 UTCGHSA enrichment
  16. 2026-09-18 10:38 UTCVendor advisory
  17. 2026-09-18 10:38 UTCGHSA enrichment
  18. 2026-09-17 23:07 UTCVendor advisory
  19. 2026-09-17 23:07 UTCGHSA enrichment
  20. 2026-09-17 19:55 UTCEG score recompute
  21. 2026-09-17 19:55 UTCVendor advisory
  22. 2026-09-17 19:55 UTCGHSA enrichment
  23. 2026-09-17 09:37 UTCVendor advisory
  24. 2026-09-17 09:37 UTCGHSA enrichment
  25. 2026-09-16 22:12 UTCVendor advisory
Show 56 more
  1. 2026-09-16 22:12 UTCGHSA enrichment
  2. 2026-09-16 21:38 UTCEG score recompute
  3. 2026-09-16 21:38 UTCVendor advisory
  4. 2026-09-16 21:38 UTCGHSA enrichment
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 10:13 UTCEG score recompute
  7. 2026-09-16 10:13 UTCVendor advisory
  8. 2026-09-16 10:13 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 22:47 UTCVendor advisory
  11. 2026-09-15 22:47 UTCGHSA enrichment
  12. 2026-09-15 18:00 UTCVendor advisory
  13. 2026-09-15 18:00 UTCGHSA enrichment
  14. 2026-09-15 13:51 UTCEG score recompute▲ 1.00
  15. 2026-09-15 13:51 UTCVendor advisory
  16. 2026-09-15 13:51 UTCGHSA enrichment
  17. 2026-09-15 13:50 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 22:58 UTCVendor advisory
  21. 2026-09-14 22:58 UTCGHSA enrichment
  22. 2026-09-14 17:50 UTCVendor advisory
  23. 2026-09-14 17:50 UTCGHSA enrichment
  24. 2026-09-14 02:22 UTCEG score recompute
  25. 2026-09-14 02:22 UTCVendor advisory
  26. 2026-09-14 02:22 UTCGHSA enrichment
  27. 2026-09-13 00:41 UTCEG score recompute
  28. 2026-09-13 00:41 UTCVendor advisory
  29. 2026-09-13 00:41 UTCGHSA enrichment
  30. 2026-09-11 22:59 UTCVendor advisory
  31. 2026-09-11 22:59 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-10 23:38 UTCEG score recompute
  40. 2026-09-10 23:38 UTCGHSA enrichment
  41. 2026-09-09 22:21 UTCGHSA enrichment
  42. 2026-09-09 20:10 UTCVendor advisory
  43. 2026-09-09 20:09 UTCGHSA enrichment
  44. 2026-09-08 23:49 UTCEG score recompute
  45. 2026-09-08 23:49 UTCVendor advisory
  46. 2026-09-08 23:49 UTCGHSA enrichment
  47. 2026-09-08 21:50 UTCEG score recompute
  48. 2026-09-08 21:50 UTCVendor advisory
  49. 2026-09-08 21:50 UTCGHSA enrichment
  50. 2026-09-08 20:42 UTCEG score recompute
  51. 2026-09-08 20:42 UTCGHSA enrichment
  52. 2026-09-08 18:58 UTCEG score recompute
  53. 2026-09-08 18:58 UTCGHSA enrichment
  54. 2026-09-08 17:55 UTCEG score recompute
  55. 2026-09-08 17:55 UTCVendor advisory
  56. 2026-09-08 17:25 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81381?
CVE-2026-81381 is a high vulnerability published on September 8, 2026. Insufficiently protected credentials in GitHub Copilot and Visual Studio Code allows an unauthorized attacker to disclose information over a network.
When was CVE-2026-81381 disclosed?
CVE-2026-81381 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-81381 actively exploited?
CVE-2026-81381 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 52.5% of all scored CVEs.
What is the CVSS score of CVE-2026-81381?
CVE-2026-81381 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-81381?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81381, 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-81381

Explore →

Is Your Infrastructure Affected by CVE-2026-81381?

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

Start Free Scan →Browse All CVEs