Affects Visual Studio Code, a widely used developer IDE; unauthenticated RCE in VS Code could broadly impact organizations and make public news.
CVE-2026-59113
Missing authorization in Visual Studio Code allows unauthenticated remote code execution.
Is CVE-2026-59113 being exploited?
Not confirmed. CVE-2026-59113 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.69% probability of exploitation in the next 30 days.
How severe is CVE-2026-59113?
CVE-2026-59113 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-59113?
Yes. A fix has been recorded for CVE-2026-59113. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-59113 affect?
CVE-2026-59113 affects Visual Studio Code (affected versions). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-59113?
Isolate/block VS Code network access, apply vendor patch when released, and monitor developer hosts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attackers can execute arbitrary code via VS Code network interface, leading to host compromise and lateral movement.
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.