Security Resilience

CVE-2026-81357

SSRF in Microsoft Visual Studio Code ≤ 1.136.2

Published
08 September 2026
Modified
11 September 2026
Patch / advisory
CVSS Score v3.1 8.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
EPSS Score 0.0051 43th percentile
Risk Priority 59 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-81357 is a high-severity SSRF (CWE-918) vulnerability in Microsoft Visual Studio Code. Its CVSS base score is 8.2 (High).

Operationally, ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-4 (Information Flow Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Server-side request forgery (ssrf) in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-21779Same product: Microsoft Visual Studio Code
CVE-2023-33144Same product: Microsoft Visual Studio Code
CVE-2025-53760Same vendor: Microsoft
CVE-2026-69683Same vendor: Microsoft
CVE-2026-88206Same vendor: Microsoft
CVE-2026-26138Same vendor: Microsoft
CVE-2023-21761Same vendor: Microsoft
CVE-2025-21385Same vendor: Microsoft
CVE-2026-45502Same vendor: Microsoft
CVE-2023-24954Same vendor: Microsoft

Affected Assets

microsoft
visual studio code
≤ 1.136.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.6
  • V1.5.3
  • V5.3.2
  • V10.4.7

Mitigating Controls (NIST 800-53 r5) AI

Information flow enforcement can restrict which destinations the server is allowed to contact on behalf of users.

Input validation directly stops untrusted URLs from being accepted and fetched without destination checks.

Boundary protection limits the network reach of server-initiated requests even if SSRF occurs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure development practices directly include input validation and destination allow-listing that prevent SSRF.

DE.CM-09 partial match
blocks

Runtime monitoring of web applications and services can detect anomalous outbound requests indicative of SSRF.

ID.RA-01 partial match
blocks

Vulnerability identification processes can discover and record SSRF flaws in web applications.

PR.IR-01 partial match
blocks

Network segmentation and egress controls can limit the damage from successful SSRF requests.

References