Visual Studio Code is widely used; SSRF can expose internal networks and sensitive data, requiring broad notification.
CVE-2026-81357
SSRF in Visual Studio Code allows network-based security bypass
Is CVE-2026-81357 being exploited?
Not confirmed. CVE-2026-81357 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-81357?
CVE-2026-81357 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-81357?
Yes. A fix has been recorded for CVE-2026-81357. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-81357 affect?
CVE-2026-81357 affects Visual Studio Code (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-81357?
Apply vendor update to VS Code immediately; restrict extension network access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Server-Side Request Forgery lets attackers make arbitrary network requests from VS Code, access internal resources, and exfiltrate data.
Immediate action required
- affected>= 1.0.0 and < 1.136.2
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.