CVE-2026-41611

CVE-2026-41611 is a high-severity vulnerability in Microsoft Visual Studio Code with a CVSS 3.x base score of 7.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-79.

Key facts

Description

Improper neutralization of script-related html tags in a web page (basic xss) in Visual Studio Code allows an unauthorized attacker to execute code locally.

Frequently asked questions

What is CVE-2026-41611?
Improper neutralization of script-related html tags in a web page (basic xss) in Visual Studio Code allows an unauthorized attacker to execute code locally.
How severe is CVE-2026-41611?
CVE-2026-41611 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-41611 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41611?
CVE-2026-41611 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-41611?
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-41611 have an EU (EUVD) identifier?
Yes. CVE-2026-41611 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-29694.
When was CVE-2026-41611 published?
CVE-2026-41611 was published on 2026-05-12 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Microsoft Visual Studio Code

All CVEs affecting Microsoft Visual Studio Code →

Other CWE-79 (Cross-site Scripting (XSS)) vulnerabilities

Browse all CWE-79 (Cross-site Scripting (XSS)) vulnerabilities →