CVE-2026-41613

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% 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
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0

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

Session fixation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
40.5%
KEV
Not listed

Published

May 12, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated May 12, 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-41613

Vendor Advisories for CVE-2026-41613(1)

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 8× in last 7d / 57× 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 142 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-41613?
CVE-2026-41613 is a high vulnerability published on May 12, 2026. Session fixation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
When was CVE-2026-41613 disclosed?
CVE-2026-41613 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41613 actively exploited?
CVE-2026-41613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 40.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41613?
CVE-2026-41613 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-41613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41613, 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-41613

Explore →

Is Your Infrastructure Affected by CVE-2026-41613?

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

Start Free Scan →Browse All CVEs