CVE-2026-81378
CVE-2026-81378 is a high-severity vulnerability in Microsoft Visual Studio Code with a CVSS 3.x base score of 8.2. 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-436.
Key facts
- Severity: High (CVSS 3.x base score 8.2)
- EPSS exploit prediction: 1% (44th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-436
- Affected product: Microsoft Visual Studio Code
- Published:
- Last modified:
Description
Interpretation conflict in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Frequently asked questions
- What is CVE-2026-81378?
- Interpretation conflict in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
- How severe is CVE-2026-81378?
- CVE-2026-81378 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity low, and availability none.
- Is CVE-2026-81378 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (44th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-81378?
- CVE-2026-81378 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-81378?
- 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.
- When was CVE-2026-81378 published?
- CVE-2026-81378 was published on 2026-09-08 and last updated on 2026-09-11.
References
Affected products (1)
- cpe:2.3:a:microsoft:visual_studio_code:*:*:*:*:*:-:*:*
More vulnerabilities in Microsoft Visual Studio Code
- CVE-2026-81376 — Critical (CVSS 9.6): Incomplete comparison with missing factors in Visual Studio Code allows an unauthorized attacker to bypass a security…
- 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-78462 — High (CVSS 8.8): Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a…
- 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.
All CVEs affecting Microsoft Visual Studio Code →
Other CWE-436 vulnerabilities
- CVE-2023-24813 — Critical (CVSS 10.0): Dompdf is an HTML to PDF converter written in php. Due to the difference in the attribute parser of Dompdf and…
- CVE-2026-63030 — Critical (CVSS 9.8): WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoint route confusion issue…
- CVE-2026-47767 — Critical (CVSS 9.8): Symfony is a PHP framework for web and console applications and a set of reusable PHP components. From 5.4.46 until…
- CVE-2026-8034 — Critical (CVSS 9.8): A server-side request forgery (SSRF) vulnerability was identified in the GitHub Enterprise Server notebook viewer that…
- CVE-2021-45327 — Critical (CVSS 9.8): Gitea before 1.11.2 is affected by Trusting HTTP Permission Methods on the Server Side when referencing the vulnerable…
- CVE-2020-10180 — Critical (CVSS 9.8): The ESET AV parsing engine allows virus-detection bypass via a crafted BZ2 Checksum field in an archive. This affects…