Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.51% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-81357High confidence
Visual Studio Code Security Feature Bypass Vulnerability
Microsoft · Visual Studio Code
8.2HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft Visual Studio Code and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
msrc_CVE-2026-81357 · CSAF 2.0 · revision 2 · finalMicrosoft Security Response CenterVisual Studio Code Security Feature Bypass Vulnerability
The vendor explicitly identifies these products as affected by this CVE.
- Visual Studio Code <1.136.2
- Summary
- Microsoft
- Remediation
- 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Server-side request forgery (ssrf) in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
What
Server-side request forgery (ssrf) in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Why
The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Server-side request forgery (ssrf) in Visual Studio Code allows an unauthorized attacker to bypass a security feature over a network.
Why
The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.
How
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Server-Side Request Forgery (SSRF) → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-918 ↗
CWE-918: Server-Side Request Forgery (SSRF). The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Visual Studio Code <1.136.2
- Action
- 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 8 Sept 2026 · Last source change 1 Oct 2026, 22:56 UTC · CWE-918 · Server-Side Request Forgery (SSRF)
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-09
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-73331
Product sourceVendor CSAF · Microsoft Security Response Center
Remediation sourceVendor CSAF · Microsoft Security Response Center
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Affected versionsThe structured affected or fixed version information changed.Microsoft Security Response Center ↗
- Before
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: 1.136.2:Security Update:https://code.visualstudio.com/updates/v1_136
- Vendor guidanceAuthoritative vendor guidance changed: added patch: msrc.microsoft.com/CVE-2026-81357; added remediation: msrc.microsoft.com/CVE-2026-81357.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- patch: msrc.microsoft.com/CVE-2026-81357 · remediation: msrc.microsoft.com/CVE-2026-81357
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
- Remediation statusRemediation status changed from Awaiting fix to Patch available.secure@microsoft.com ↗
- Before
- Awaiting fix
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 1.0.0 < 1.136.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- Visual Studio Code: 1.0.0 < 1.136.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- ENISA EUVD mappingEUVD-2026-73331 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-73331"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.