CVE-2026-70188
ASP.NET Core 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.13, 11.0.0-rc.2, 8.0.32, 9.0.21, 17.14.42, and 1 more
- 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: yes
- Technical impact: total
Summary
Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows an unauthorized attacker to bypass a security feature over a network.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- CVE published
- Record last updated
Affected versions
- Microsoft ASP.NET Core 10.0
From 10.0 · fixed in 10.0.13
- Microsoft ASP.NET Core 11.0
From 11.0 · fixed in 11.0.0-rc.2
- Microsoft ASP.NET Core 8.0
From 8.0 · fixed in 8.0.32
- Microsoft ASP.NET Core 9.0
From 9.0 · fixed in 9.0.21
- Microsoft Microsoft Visual Studio 2022 version 17.14
From 17.14.0 · fixed in 17.14.42
- Microsoft Microsoft Visual Studio 2026 version 18.10
From 18.10.0 · fixed in 18.10.4