CVE-2026-57102
VS Code vulnerability allows remote bypass of security controls over network.
Is CVE-2026-57102 being exploited?
Not confirmed. CVE-2026-57102 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.82% probability of exploitation in the next 30 days.
How severe is CVE-2026-57102?
CVE-2026-57102 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-57102?
Yes. A fix has been recorded for CVE-2026-57102. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-57102 affect?
CVE-2026-57102 affects Microsoft Visual Studio Code. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-57102?
Apply vendor patch when released; restrict VS Code network access and untrusted extensions.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can bypass VS Code security controls over the network to perform unauthorized actions, potentially access data or execute code via the IDE.
Patch when possible
- affected>= 1.0.0 and < 1.128.1
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.