CVE-2026-62899
.NET Security Feature Bypass Vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 10.0.11, 8.0.30, 9.0.19, 17.14.38, 18.8.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Inconsistent interpretation of http requests ('http request/response smuggling') in .NET allows an unauthorized attacker to bypass a security feature over a network.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Microsoft .NET 10.0 runtime
From 10.0.0 · fixed in 10.0.11
- Microsoft .NET 8.0 runtime
From 8.0.0 · fixed in 8.0.30
- Microsoft .NET 9.0 runtime
From 9.0.0 · fixed in 9.0.19
- Microsoft Microsoft Visual Studio 2022 version 17.14
From 17.14.0 · fixed in 17.14.38
- Microsoft Microsoft Visual Studio 2026 version 18.8
From 18.0 · fixed in 18.8.3