Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-88092 Overview
CVE-2026-88092 is an HTTP request smuggling vulnerability in ASP.NET Core caused by inconsistent interpretation of HTTP requests between upstream proxies and the server. An unauthorized remote attacker can tamper with requests across trust boundaries without authentication or user interaction. The flaw is tracked under CWE-444 (Inconsistent Interpretation of HTTP Requests).
Microsoft published the advisory through the Microsoft Security Response Center. The vulnerability affects applications that place ASP.NET Core behind a reverse proxy or load balancer, where differences in request parsing enable smuggled payloads.
Critical Impact
An unauthenticated network attacker can bypass front-end security controls, poison caches, and tamper with requests processed by ASP.NET Core services.
Affected Products
- ASP.NET Core (versions listed in the Microsoft advisory)
- Applications hosted on Kestrel behind HTTP/1.1 proxies
- .NET-based web services exposed through load balancers or CDNs
Discovery Timeline
- 2026-10-13 - CVE-2026-88092 published to the National Vulnerability Database
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-88092
Vulnerability Analysis
The vulnerability stems from inconsistent HTTP message framing between ASP.NET Core and upstream HTTP intermediaries. When a proxy and the server disagree on where one request ends and the next begins, an attacker can hide a second request inside the body of the first. The hidden request bypasses front-end filtering and is processed by the back-end with unexpected context.
Exploitation targets request-smuggling classes such as CL.TE, TE.CL, or TE.TE conflicts, depending on how the proxy and Kestrel handle Content-Length and Transfer-Encoding headers. Successful smuggling allows attackers to tamper with other users' requests, poison shared caches, bypass authentication filters, and route traffic to unintended endpoints. Because the attack operates at the HTTP protocol layer, standard application-level input validation does not block it.
Root Cause
The root cause is divergent parsing of HTTP/1.1 framing headers between ASP.NET Core and upstream proxies. Ambiguous or conflicting Transfer-Encoding and Content-Length values are interpreted differently on each hop, violating RFC 7230 framing requirements. This inconsistency allows a crafted request to be split into two distinct requests at the server boundary.
Attack Vector
The attack is remote and unauthenticated over the network. An attacker sends a single crafted HTTP/1.1 request through a proxy that fronts the ASP.NET Core application. The proxy forwards the request as one message while Kestrel parses it as two, with the smuggled portion treated as the start of the next connection-reused request. The result is tampering with request routing, cache state, or the identity bound to a subsequent request. See the Microsoft Security Update CVE-2026-88092 advisory for vendor technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-88092
Indicators of Compromise
- HTTP/1.1 requests containing both Content-Length and Transfer-Encoding: chunked headers reaching ASP.NET Core services
- Unexpected HTTP methods or paths in server logs that do not correspond to any proxy access log entry
- Cache entries serving responses that do not match the originating request URL
- Anomalous spikes in 400 Bad Request responses from Kestrel following malformed framing
Detection Strategies
- Inspect reverse-proxy and Kestrel logs for mismatched request counts across the same TCP connection
- Alert on requests containing duplicate or obfuscated Transfer-Encoding headers such as Transfer-Encoding: xchunked or whitespace variants
- Deploy a web application firewall rule that rejects requests presenting both Content-Length and Transfer-Encoding
Monitoring Recommendations
- Correlate front-end proxy access logs with back-end ASP.NET Core request logs to detect request-count divergence
- Monitor for sudden changes in authenticated session behavior that could indicate cross-user request tampering
- Track egress responses from cache layers for content served to the wrong URL or user context
How to Mitigate CVE-2026-88092
Immediate Actions Required
- Apply the ASP.NET Core security update referenced in the Microsoft Security Update CVE-2026-88092 advisory
- Inventory all internet-facing ASP.NET Core services fronted by proxies, CDNs, or load balancers
- Validate that upstream proxies normalize or reject ambiguous HTTP framing before patching back-end hosts
Patch Information
Microsoft has released fixed ASP.NET Core packages through the Microsoft Update channel. Administrators should install the latest .NET runtime and ASP.NET Core shared framework updates from Microsoft Update, the .NET installer, or NuGet, then redeploy affected applications. Refer to the Microsoft Security Update CVE-2026-88092 advisory for the exact fixed versions.
Workarounds
- Disable HTTP/1.1 connection reuse between the proxy and Kestrel until the patch is applied
- Configure the upstream proxy to reject requests containing both Content-Length and Transfer-Encoding headers
- Terminate TLS and parse HTTP at a hardened reverse proxy that normalizes framing before forwarding to ASP.NET Core
# Update ASP.NET Core runtime to the patched version
dotnet --list-runtimes
# Install the patched runtime per Microsoft advisory, then restart services
sudo systemctl restart kestrel-myapp.service
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

