CVE-2026-54981

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

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

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

Inclusion of functionality from untrusted control sphere in Visual Studio Code - Python extension allows an unauthorized attacker to bypass a security feature locally.

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

Published

August 11, 2026

Last Modified

September 16, 2026

Advisory Details (1)

Auto-updated Aug 11, 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-54981

Vendor Advisories for CVE-2026-54981(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 41× in last 7d / 195× 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.

Showing the most recent 100 of 318 total refreshes for this CVE.

  1. 2026-09-19 13:07 UTCVendor advisory
  2. 2026-09-19 13:07 UTCGHSA enrichment
  3. 2026-09-19 01:03 UTCEG score recompute
  4. 2026-09-19 01:03 UTCVendor advisory
  5. 2026-09-19 01:03 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 12:58 UTCVendor advisory
  8. 2026-09-18 12:58 UTCGHSA enrichment
  9. 2026-09-18 00:40 UTCEG score recompute
  10. 2026-09-18 00:40 UTCVendor advisory
  11. 2026-09-18 00:40 UTCGHSA enrichment
  12. 2026-09-17 19:31 UTCEPSS rescore
  13. 2026-09-17 05:07 UTCVendor advisory
  14. 2026-09-17 05:07 UTCGHSA enrichment
  15. 2026-09-16 17:03 UTCEG score recompute
  16. 2026-09-16 17:03 UTCVendor advisory
  17. 2026-09-16 17:03 UTCGHSA enrichment
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 10:56 UTCEG score recompute
  20. 2026-09-16 10:56 UTCVendor advisory
  21. 2026-09-16 10:56 UTCGHSA enrichment
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 22:42 UTCVendor advisory
  24. 2026-09-15 22:42 UTCGHSA enrichment
  25. 2026-09-15 06:28 UTCEG score recompute
Show 75 more
  1. 2026-09-15 06:28 UTCVendor advisory
  2. 2026-09-15 06:28 UTCGHSA enrichment
  3. 2026-09-15 03:11 UTCEPSS rescore
  4. 2026-09-14 18:01 UTCVendor advisory
  5. 2026-09-14 18:01 UTCGHSA enrichment
  6. 2026-09-14 05:37 UTCVendor advisory
  7. 2026-09-14 05:37 UTCGHSA enrichment
  8. 2026-09-13 17:34 UTCEG score recompute
  9. 2026-09-13 17:34 UTCVendor advisory
  10. 2026-09-13 17:33 UTCGHSA enrichment
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-13 05:29 UTCVendor advisory
  13. 2026-09-13 05:29 UTCGHSA enrichment
  14. 2026-09-12 17:25 UTCEG score recompute
  15. 2026-09-12 17:25 UTCVendor advisory
  16. 2026-09-12 17:25 UTCGHSA enrichment
  17. 2026-09-12 05:21 UTCVendor advisory
  18. 2026-09-12 05:21 UTCGHSA enrichment
  19. 2026-09-11 17:17 UTCVendor advisory
  20. 2026-09-11 17:17 UTCGHSA enrichment
  21. 2026-09-11 16:01 UTCVendor advisory
  22. 2026-09-11 16:01 UTCGHSA enrichment
  23. 2026-09-11 15:38 UTCEG score recompute
  24. 2026-09-11 15:38 UTCVendor advisory
  25. 2026-09-11 15:38 UTCGHSA enrichment
  26. 2026-09-11 14:53 UTCEPSS rescore
  27. 2026-09-11 04:10 UTCEG score recompute
  28. 2026-09-11 04:10 UTCGHSA enrichment
  29. 2026-09-10 16:06 UTCEG score recompute
  30. 2026-09-10 16:06 UTCGHSA enrichment
  31. 2026-09-10 09:35 UTCEPSS rescore
  32. 2026-09-10 09:16 UTCGHSA enrichment
  33. 2026-09-09 20:54 UTCVendor advisory
  34. 2026-09-09 20:54 UTCGHSA enrichment
  35. 2026-09-09 10:38 UTCVendor advisory
  36. 2026-09-09 10:38 UTCGHSA enrichment
  37. 2026-09-08 22:12 UTCEG score recompute
  38. 2026-09-08 22:12 UTCVendor advisory
  39. 2026-09-08 22:12 UTCGHSA enrichment
  40. 2026-09-08 22:01 UTCEPSS rescore
  41. 2026-09-08 18:23 UTCVendor advisory
  42. 2026-09-08 18:23 UTCGHSA enrichment
  43. 2026-09-08 07:13 UTCVendor advisory
  44. 2026-09-08 07:13 UTCGHSA enrichment
  45. 2026-09-07 18:44 UTCEG score recompute
  46. 2026-09-07 18:44 UTCVendor advisory
  47. 2026-09-07 18:44 UTCGHSA enrichment
  48. 2026-09-07 16:01 UTCEPSS rescore
  49. 2026-09-07 06:40 UTCVendor advisory
  50. 2026-09-07 06:40 UTCGHSA enrichment
  51. 2026-09-06 14:37 UTCEG score recompute
  52. 2026-09-06 14:37 UTCVendor advisory
  53. 2026-09-06 14:37 UTCGHSA enrichment
  54. 2026-09-06 13:47 UTCEPSS rescore
  55. 2026-09-06 02:34 UTCEG score recompute
  56. 2026-09-06 02:34 UTCVendor advisory
  57. 2026-09-06 02:33 UTCGHSA enrichment
  58. 2026-09-05 14:29 UTCVendor advisory
  59. 2026-09-05 14:29 UTCGHSA enrichment
  60. 2026-09-05 01:32 UTCEG score recompute
  61. 2026-09-05 01:32 UTCVendor advisory
  62. 2026-09-05 01:32 UTCGHSA enrichment
  63. 2026-09-04 10:01 UTCEG score recompute
  64. 2026-09-04 10:01 UTCVendor advisory
  65. 2026-09-04 10:01 UTCGHSA enrichment
  66. 2026-09-04 05:06 UTCEPSS rescore
  67. 2026-09-03 21:44 UTCVendor advisory
  68. 2026-09-03 21:44 UTCGHSA enrichment
  69. 2026-09-03 15:42 UTCVendor advisory
  70. 2026-09-03 15:42 UTCGHSA enrichment
  71. 2026-09-03 08:05 UTCVendor advisory
  72. 2026-09-03 08:05 UTCGHSA enrichment
  73. 2026-09-02 19:30 UTCVendor advisory
  74. 2026-09-02 19:30 UTCGHSA enrichment
  75. 2026-09-02 18:22 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-54981?
CVE-2026-54981 is a high vulnerability published on August 11, 2026. Inclusion of functionality from untrusted control sphere in Visual Studio Code - Python extension allows an unauthorized attacker to bypass a security feature locally.
When was CVE-2026-54981 disclosed?
CVE-2026-54981 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54981 actively exploited?
CVE-2026-54981 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 66.7% of all scored CVEs.
What is the CVSS score of CVE-2026-54981?
CVE-2026-54981 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-54981?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54981, 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-54981

Explore →

Is Your Infrastructure Affected by CVE-2026-54981?

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