Skip to main content
Vulnerability Database/CVE-2026-70188

CVE-2026-70188: ASP.NET Core Auth Bypass Vulnerability

CVE-2026-70188 is an authentication bypass flaw in ASP.NET Core caused by HTTP request smuggling that enables unauthorized attackers to circumvent security features. This article covers technical details, affected versions, impact assessment, and mitigation strategies.

Published:

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-70188 Overview

CVE-2026-70188 is an HTTP request smuggling vulnerability in ASP.NET Core caused by inconsistent interpretation of HTTP requests. An unauthorized attacker can bypass a security feature over the network without authentication or user interaction. The flaw is tracked under CWE-444: Inconsistent Interpretation of HTTP Requests.

Microsoft published the advisory on October 13, 2026. The vulnerability allows attackers to desynchronize how front-end proxies and back-end ASP.NET Core servers parse the same HTTP request stream, enabling security control bypass against hosted applications.

Critical Impact

Remote, unauthenticated attackers can smuggle crafted HTTP requests through ASP.NET Core to bypass security filters, poison caches, or hijack sessions handled by downstream components.

Affected Products

  • ASP.NET Core (versions enumerated in the Microsoft advisory)
  • Applications hosted on Kestrel or in-process IIS behind reverse proxies
  • Any downstream services relying on ASP.NET Core's HTTP parsing for security decisions

Discovery Timeline

  • 2026-10-13 - CVE-2026-70188 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-70188

Vulnerability Analysis

HTTP request smuggling occurs when two HTTP processors in a request chain disagree on where one request ends and the next begins. In this case, ASP.NET Core's HTTP parser interprets request boundaries differently from upstream proxies, load balancers, or content delivery networks. An attacker crafts a single TCP payload that one component treats as one request while the other treats as two.

The smuggled request bypasses perimeter controls because the front-end never inspects it as a standalone request. The ASP.NET Core back-end then processes the smuggled portion with full application privileges. This enables bypass of authentication filters, Web Application Firewall (WAF) rules, and routing-based access controls.

Successful exploitation can lead to session hijacking, cache poisoning, credential theft from queued requests, and unauthorized access to internal endpoints. The attack is unauthenticated and network-reachable wherever the ASP.NET Core server sits behind a differing HTTP intermediary.

Root Cause

The root cause is inconsistent parsing of HTTP framing headers such as Content-Length and Transfer-Encoding. ASP.NET Core resolves ambiguous or conflicting framing in a manner that does not match common front-end proxies, producing a desynchronization condition classified as [CWE-444].

Attack Vector

The attack is delivered over the network against the HTTP listener. No authentication, privileges, or user interaction are required. The attacker sends a single malformed HTTP request containing conflicting or malformed framing directives to the front-end, which forwards it unchanged to the ASP.NET Core server.

See the Microsoft Security Update Guide for CVE-2026-70188 for technical specifics on the affected parsing logic and fixed versions.

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 Attacks

Detection Methods for CVE-2026-70188

Indicators of Compromise

  • HTTP requests containing both Content-Length and Transfer-Encoding: chunked headers in the same message
  • Malformed chunked encoding, obfuscated Transfer-Encoding header casing, or duplicated framing headers
  • Unexpected secondary requests appearing in ASP.NET Core logs with no corresponding front-end proxy log entry
  • Session or cache anomalies where authenticated responses are served to unrelated clients

Detection Strategies

  • Compare request logs between the front-end proxy and ASP.NET Core Kestrel to identify request count mismatches
  • Alert on requests containing conflicting framing headers at the WAF or reverse proxy layer
  • Inspect application telemetry for sudden spikes in 400-class responses tied to specific client IPs
  • Correlate authentication events with unexpected URL paths processed by the same connection

Monitoring Recommendations

  • Enable verbose HTTP parsing logs on Kestrel and ingest them into a centralized analytics platform
  • Monitor the ratio of upstream to downstream request counts per connection as a desynchronization signal
  • Track outbound response sizes for anomalies consistent with cache poisoning

How to Mitigate CVE-2026-70188

Immediate Actions Required

  • Apply the ASP.NET Core security update referenced in the Microsoft Security Update Guide
  • Inventory all internet-facing services running ASP.NET Core, including containerized workloads
  • Configure front-end proxies to reject requests with ambiguous framing headers
  • Review WAF rulesets to drop requests containing both Content-Length and Transfer-Encoding headers

Patch Information

Microsoft has released updated ASP.NET Core runtime and SDK packages addressing the parsing inconsistency. Administrators should install the fixed versions listed in the Microsoft advisory and redeploy affected applications. Self-contained deployments must be rebuilt against the patched runtime because the vulnerable parser is bundled with the application.

Workarounds

  • Terminate HTTP/1.1 traffic at a hardened reverse proxy that normalizes framing headers before forwarding to Kestrel
  • Disable Transfer-Encoding: chunked support at the edge where it is not required by application logic
  • Enforce HTTP/2 end-to-end between the proxy and ASP.NET Core to eliminate chunked-encoding desync vectors
bash
# Configuration example: reject conflicting framing headers at NGINX front-end
http {
    map $http_transfer_encoding $block_smuggling {
        default 0;
        "~*chunked" 1;
    }

    server {
        listen 443 ssl http2;
        if ($http_content_length != "") {
            set $has_cl 1;
        }
        if ($block_smuggling = 1) {
            set $has_te 1;
        }
        if ($has_cl$has_te = "11") {
            return 400;
        }
        location / {
            proxy_pass http://aspnetcore_backend;
        }
    }
}

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.