CVE-2026-69278
CVE-2026-69278 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-693.
Key facts
- Severity: High (CVSS 3.x base score 7.8)
- EPSS exploit prediction: 0% (23rd percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-693
- Affected product: Microsoft Visual Studio Code
- Published:
- Last modified:
Description
Incorrect authorization in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.
Frequently asked questions
- What is CVE-2026-69278?
- Incorrect authorization in Visual Studio Code allows an unauthorized attacker to bypass a security feature locally.
- How severe is CVE-2026-69278?
- CVE-2026-69278 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-69278 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-69278?
- CVE-2026-69278 affects Microsoft Visual Studio Code. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-69278?
- 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-69278 published?
- CVE-2026-69278 was published on 2026-08-11 and last updated on 2026-09-25.
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-693 (Protection Mechanism Failure) vulnerabilities
- CVE-2026-93606 — Critical (CVSS 10.0): vm2 (npm) versions 3.12.0 and earlier contain a sandbox escape in `VM` and `NodeVM`. When an embedder exposes a host…
- CVE-2026-93605 — Critical (CVSS 10.0): vm2 NodeVM versions before 3.12.1 contain a sandbox escape vulnerability where the DANGEROUS_BUILTINS denylist omits…
- CVE-2026-92956 — Critical (CVSS 10.0): vm2 versions 3.10.1 through 3.11.6 contain a sandbox escape reachable from a default `new VM()` sandbox when running on…
- CVE-2026-75874 — Critical (CVSS 10.0): Sandbox escape in the Remote Settings Client component. This vulnerability was fixed in Firefox 154, Thunderbird 154,…
- CVE-2026-47140 — Critical (CVSS 10.0): vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM blocks several dangerous Node.js builtins…
- CVE-2026-34208 — Critical (CVSS 10.0): SandboxJS is a JavaScript sandboxing library. Prior to 0.8.36, SandboxJS blocks direct assignment to global objects…
Browse all CWE-693 (Protection Mechanism Failure) vulnerabilities →