How severe is CVE-2026-41613?

CVE-2026-41613 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-41613 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-41613?

CVE-2026-41613 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-41613?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-41613 have an EU (EUVD) identifier?

Yes. CVE-2026-41613 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-29696.

When was CVE-2026-41613 published?

CVE-2026-41613 was published on 2026-05-12 and last updated on 2026-06-17.

CVE-2026-41613

CVE-2026-41613 is a high-severity vulnerability in Microsoft Visual Studio Code with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-384.

Key facts

Severity: High (CVSS 3.x base score 8.8)
EPSS exploit prediction: 1% (42nd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-29696
Weakness: CWE-384
Affected product: Microsoft Visual Studio Code
Published: 2026-05-12
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2026-41613?: Session fixation in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
How severe is CVE-2026-41613?: CVE-2026-41613 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-41613 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (42nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41613?: CVE-2026-41613 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-41613?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-41613 have an EU (EUVD) identifier?: Yes. CVE-2026-41613 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-29696.
When was CVE-2026-41613 published?: CVE-2026-41613 was published on 2026-05-12 and last updated on 2026-06-17.

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41613

Affected products (1)

cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Visual Studio Code

CVE-2026-47281 — Critical (CVSS 9.6): Missing authorization in Visual Studio Code allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-70336 — High (CVSS 8.8): Improper control of generation of code ('code injection') in Visual Studio Code allows an unauthorized attacker to…
CVE-2026-69320 — High (CVSS 8.8): Improper neutralization of special elements used in an os command ('os command injection') in Visual Studio Code allows…
CVE-2026-59113 — High (CVSS 8.8): Missing authorization in Visual Studio Code allows an unauthorized attacker to execute code over a network.
CVE-2026-57102 — High (CVSS 8.8): Inclusion of functionality from untrusted control sphere in Visual Studio Code allows an unauthorized attacker to…
CVE-2026-41109 — High (CVSS 8.8): Improper neutralization of special elements in output used by a downstream component ('injection') in GitHub Copilot…

All CVEs affecting Microsoft Visual Studio Code →

Other CWE-384 (Session Fixation) vulnerabilities

CVE-2024-11317 — Critical (CVSS 10.0): Session Fixation vulnerabilities allow an attacker to fix a users session identifier before login providing an…
CVE-2024-38513 — Critical (CVSS 10.0): Fiber is an Express-inspired web framework written in Go A vulnerability present in versions prior to 2.52.5 is a…
CVE-2021-20151 — Critical (CVSS 10.0): Trendnet AC2600 TEW-827DRU version 2.08B01 contains a flaw in the session management for the device. The router's…
CVE-2021-32088 — Critical (CVSS 9.8): An issue was discovered in Quest KACE Systems Deployment Appliance (SMA) 11.0.273. Certain API endpoints contain a…
CVE-2025-67446 — Critical (CVSS 9.8): Improper Authentication (Authentication Bypass) exists in Neterbit NW-431F Router 20241014-IR03 and before. The router…
CVE-2026-25101 — Critical (CVSS 9.8): Bludit allows user's session identifier to be set before authentication. The value of this session ID stays the same…

Browse all CWE-384 (Session Fixation) vulnerabilities →