CVE-2026-78462
CVE-2026-78462 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-639.
Key facts
- Severity: High (CVSS 3.x base score 8.8)
- EPSS exploit prediction: 1% (56th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-639
- Affected product: Microsoft Visual Studio Code
- Published:
- Last modified:
Description
Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Frequently asked questions
- What is CVE-2026-78462?
- Authorization bypass through user-controlled key in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
- How severe is CVE-2026-78462?
- CVE-2026-78462 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-78462 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (56th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-78462?
- CVE-2026-78462 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-78462?
- 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-78462 published?
- CVE-2026-78462 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-102238 — Critical (CVSS 9.6): Improper limitation of a pathname to a restricted directory ('path traversal') in Visual Studio Code allows an…
- 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-70098 — High (CVSS 8.8): Missing authorization in Visual Studio Code allows an unauthorized attacker to execute code over a network.
- CVE-2026-102235 — High (CVSS 8.8): Improper encoding or escaping of output in Visual Studio Code allows an unauthorized attacker to execute code over 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…
All CVEs affecting Microsoft Visual Studio Code →
Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities
- CVE-2026-109469 — Critical (CVSS 10.0): Authorization bypass through user-controlled key in Entra Device Registration allows an unauthorized attacker to…
- CVE-2024-34323 — Critical (CVSS 10.0): ProPhoenix Law RMS v2022.2403.3.101 was discovered to contain an Insecure Direct Object Reference (IDOR) via the…
- CVE-2026-69865 — Critical (CVSS 10.0): Authorization bypass through user-controlled key in Microsoft Container Registry allows an unauthorized attacker to…
- CVE-2026-83711 — Critical (CVSS 10.0): Authorization bypass through user-controlled key in Microsoft Azure Active Directory B2C allows an unauthorized…
- CVE-2026-77998 — Critical (CVSS 10.0): Joomla Extension - miniorange.com - Unauthenticated Authentication Bypass via SAMLResponse Parameter in miniOrange SAML…
- CVE-2026-77995 — Critical (CVSS 10.0): Joomla Extension - miniorange.com - Arbitrary account takeover in miniOrange OAuth Client < 3.2.0, OAuth Single Sign-On…
Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →