CVE-2026-69306
VS Code failing-open allows remote bypass of a security control.
Is CVE-2026-69306 being exploited?
Not confirmed. CVE-2026-69306 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-69306?
CVE-2026-69306 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-69306?
Yes. A fix has been recorded for CVE-2026-69306. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-69306 affect?
CVE-2026-69306 affects Visual Studio Code (desktop), VS Code Remote/Server features (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-69306?
Update to vendor patch when released; meanwhile disable remote/server features and restrict network access to VS Code.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can bypass VS Code security checks over the network, enabling unauthorized access to workspace resources, extensions, or execution of actions.
Patch when possible
- affected>= 1.0.0 and < 1.135
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.