Skip to main content
EPSS 0.5%top 57%

CVE-2026-81357: CWE-918: Server-Side Request Forgery (SSRF) in Microsoft Visual Studio Code

0
High
VulnerabilityCVE-2026-81357cvecve-2026-81357cwe-918
Published: 09/08/2026 (09/08/2026, 17:13:56 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Visual Studio Code

Description

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

CVSS v3.1

Score 8.2high

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:C

Affected software

Microsoft

Visual Studio Code

Affected versions
>=1.0.0 <1.136.2
GitHub Actionsmore threats →ai
microsoft/vscode
pkg:github/microsoft/vscode
Affected versions
=1.0.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/14/2026, 22:06:14 UTC

Technical Analysis

This vulnerability, identified as CWE-918 (Server-Side Request Forgery), exists in Microsoft Visual Studio Code and enables an unauthorized attacker to bypass security controls over a network. The CVSS 3.1 base score is 8.2, indicating high severity, with network attack vector, low attack complexity, no privileges required, user interaction required, scope changed, high confidentiality impact, low integrity impact, and no availability impact. The vulnerability affects versions >=1.0.0 and <1.136.2. Microsoft has released an official fix to address this issue.

Potential Impact

An attacker can exploit this SSRF vulnerability to bypass security features remotely, potentially gaining access to sensitive information (high confidentiality impact) and causing limited integrity issues. There is no impact on system availability. The vulnerability does not require privileges but does require user interaction. The scope of the vulnerability is changed, indicating that the attack can affect resources beyond the initially vulnerable component.

Mitigation Recommendations

Microsoft has released an official fix for this vulnerability. Users should update Visual Studio Code to version 1.136.2 or later to remediate the issue. No additional mitigation steps are required beyond applying the official patch.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2026-08-26T18:40:19.856Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
official-fix
Vendor Advisory Urls
[{"url":"https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-81357","vendor":"Microsoft"}]

Threat ID: 6aa0456aacd9273b49facec1

Added to database: 09/08/2026, 17:27:06 UTC

Last enriched: 10/14/2026, 22:06:14 UTC

Last updated: 10/23/2026, 15:10:15 UTC

Views: 70

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses