Remote code execution in Microsoft Visual Studio Code, a widely used developer tool; could enable broad compromise of developer machines and CI workflows, meriting org-wide attention.
CVE-2026-70336
Remote code execution via code injection in Visual Studio Code.
Is CVE-2026-70336 being exploited?
Not confirmed. CVE-2026-70336 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.61% probability of exploitation in the next 30 days.
How severe is CVE-2026-70336?
CVE-2026-70336 is rated High with a CVSS score of 8.8. 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-70336?
Yes. A fix has been recorded for CVE-2026-70336. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-70336 affect?
CVE-2026-70336 affects Visual Studio Code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-70336?
Apply vendor patch when available; disable remote/extension features and restrict VS Code network access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution over the network via code injection; attacker can run arbitrary code in the user's context or affected process.
Immediate action required
- 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.