Security bypass via inconsistent HTTP request parsing
Published Sep 8, 2026 · Updated Sep 10, 2026
HTTP request smuggling in Microsoft Visual Studio Code before 1.136.2 allows remote attackers to bypass a security feature over a network. Microsoft has not disclosed which HTTP-handling component interprets crafted request boundaries inconsistently or which security control is bypassed. Exploitation requires user interaction but no privileges and can expose or alter data across a changed security scope without interrupting availability.
Summary
What happened
HTTP request smuggling in Microsoft Visual Studio Code before 1.136.2 allows remote attackers to bypass a security feature over a network. Microsoft has not disclosed which HTTP-handling component interprets crafted request boundaries inconsistently or which security control is bypassed. Exploitation requires user interaction but no privileges and can expose or alter data across a changed security scope without interrupting availability.
The record
- CVE
- CVE-2026-81356
- Published
- Sep 8, 2026
- Updated
- Sep 10, 2026
- Vendor
- Microsoft
- Product
- Visual Studio Code
- Classifications
- CWE-444, CAPEC-33, CAPEC-273
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.136.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo