Skip to content
CVE-2026-88092 IBM QRadar · QRadar

Detect CVE-2026-88092 - ASP.NET Core HTTP Request Smuggling / Security Feature Bypass in IBM QRadar

Detects potential exploitation and exposure of CVE-2026-88092, an ASP.NET Core security feature bypass (CWE-444, HTTP request/response smuggling) with CVSS 9.4. Vulnerable Microsoft.AspNetCore.App.Runtime packages (8.0.0-8.0.31, 9.0.0-9.0.20, 10.0.0-10.0.12, 11.0.0-preview.1 through 11.0.0-rc.1) inconsistently interpret HTTP message boundaries, allowing an attacker to smuggle requests past front-end security controls (WAF, auth proxies, routing). Exploitation is theoretical at disclosure; detection focuses on inventorying vulnerable runtimes and on HTTP traffic anomalies indicative of request smuggling (ambiguous Content-Length/Transfer-Encoding, duplicated headers, desync-style request pairs).

MITRE ATT&CK

Tactic
Initial Access Stealth

QRadar Detection Query

IBM QRadar (QRadar)
sql
-- df00tech DF00-d17b1f3c73 · https://df00tech.com/detections/CVE-2026-88092 · licence: https://df00tech.com/detections/licence
SELECT sourceip, destinationip, "URL", "HTTP Response Code", COUNT(*) AS hits FROM events WHERE LOGSOURCETYPENAME(devicetype) ILIKE '%IIS%' AND ( UTF8(payload) ILIKE '%Transfer-Encoding%' AND UTF8(payload) ILIKE '%Content-Length%' OR "HTTP Response Code" IN (400,501) ) GROUP BY sourceip, destinationip, "URL", "HTTP Response Code" HAVING COUNT(*) > 15 LAST 24 HOURS
medium severity low confidence

Identifies ASP.NET Core / IIS web traffic with conflicting HTTP framing headers or elevated protocol-error responses indicative of CVE-2026-88092 smuggling attempts.

Data Sources

IIS LogsWeb Proxy

Required Tables

events

False Positives & Tuning

  • Benign re-chunking proxies in the request path
  • Scanner-generated 400/501 bursts
  • Legacy clients with malformed headers

Other platforms for CVE-2026-88092


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are further down this page.

  1. Test 1 Enumerate ASP.NET Core runtime versions

    Expected signal: Process execution of dotnet with --list-runtimes; output lines containing Microsoft.AspNetCore.App versions.

  2. Test 2 Send ambiguously-framed HTTP request (CL.TE)

    Expected signal: Web/Kestrel log entry showing both Content-Length and Transfer-Encoding headers; likely 400/501 response.

  3. Test 3 Locate vulnerable Kestrel DLL on Windows host

    Expected signal: DeviceFileEvents/FileWritten access to Kestrel DLL; PowerShell process execution reading file version.


Response Playbook

Triage

  1. Confirm the affected host runs a vulnerable Microsoft.AspNetCore.App.Runtime version (8.0.0-8.0.31, 9.0.0-9.0.20, 10.0.0-10.0.12, or 11.0.0-preview.1 to rc.1) via the endpoint inventory query.
  2. Determine whether the host is internet-facing or behind a shared front-end proxy/WAF, since request smuggling impact depends on an intermediary that re-interprets boundaries.
  3. Review web/Kestrel logs for the flagged source IPs for requests containing both Content-Length and Transfer-Encoding headers or duplicated length headers correlated with 400/501 responses.

Containment

  1. Apply the patched runtime (8.0.32 / 9.0.21 / 10.0.13 / 11.0.0-rc.2 or later) and restart the affected Kestrel/IIS services.
  2. If immediate patching is not possible, configure the front-end proxy/WAF to reject requests containing both Transfer-Encoding and Content-Length, and normalize/strip ambiguous framing headers.

Evidence Collection

  1. Capture full web server and Kestrel request logs for the implicated time window, preserving raw headers and response codes.
  2. Export the endpoint file inventory showing the exact DLL file version and path for chain-of-custody and patch verification.

Escalation Criteria

  • !Escalate to IR if smuggled requests correlate with authentication bypass, access to restricted endpoints, or cache poisoning of shared responses.
  • !Escalate if the vulnerable runtime is confirmed on internet-facing production hosts behind a shared proxy before patching can be completed.

Investigation Guide

Forensic Artifacts

  • >Kestrel and IIS raw request logs showing conflicting Content-Length/Transfer-Encoding headers
  • >File version metadata of Microsoft.AspNetCore.App.Runtime / Kestrel DLLs on the host
  • >Proxy/WAF logs showing request/response desynchronization or unexpected response pairing

Tuning Guidance

Baseline legitimate intermediaries that legitimately re-chunk traffic and exclude their IPs. Raise the 400/501 count thresholds for high-traffic APIs, and prioritize alerts on hosts confirmed to run vulnerable runtime versions behind a shared front-end proxy. Suppress endpoint-inventory matches once patched versions are confirmed deployed.


Hunting Queries

Hunt for HTTP requests carrying both framing headers or elevated protocol errors against ASP.NET Core/IIS hosts.

Hunting — KQL
kql
// df00tech DF00-d17b1f3c73 · https://df00tech.com/detections/CVE-2026-88092 · licence: https://df00tech.com/detections/licence
W3CIISLog | where csReferer has "Transfer-Encoding" or scStatus in (400,501) | summarize c=count() by cIP, csUriStem, bin(TimeGenerated,10m) | where c > 20
Hunting — SPL
spl
``` df00tech DF00-d17b1f3c73 · https://df00tech.com/detections/CVE-2026-88092 · licence: https://df00tech.com/detections/licence ```
index=web sourcetype=iis | regex _raw="(?i)(Transfer-Encoding.*Content-Length|Content-Length.*Transfer-Encoding)" | stats count by c_ip, host

Atomic Red Team Tests

Test 1 Enumerate ASP.NET Core runtime versions
linux

List installed .NET/ASP.NET Core runtimes to identify vulnerable versions in a lab host.

Command

bash
dotnet --list-runtimes | grep -i 'Microsoft.AspNetCore.App'

Cleanup

bash
echo 'no cleanup required - read-only enumeration'

Expected Telemetry

Process execution of dotnet with --list-runtimes; output lines containing Microsoft.AspNetCore.App versions.

Expected Detection

Endpoint inventory query flags any listed version within 8.0.0-8.0.31, 9.0.0-9.0.20, or 10.0.0-10.0.12.

Test 2 Send ambiguously-framed HTTP request (CL.TE)
linux

Send a request containing both Content-Length and Transfer-Encoding headers to a lab ASP.NET Core endpoint to simulate a smuggling probe.

Command

bash
printf 'POST / HTTP/1.1\r\nHost: lab.local\r\nContent-Length: 6\r\nTransfer-Encoding: chunked\r\n\r\n0\r\n\r\nG' | nc lab.local 80

Cleanup

bash
echo 'no cleanup required - transient network request'

Expected Telemetry

Web/Kestrel log entry showing both Content-Length and Transfer-Encoding headers; likely 400/501 response.

Expected Detection

KQL/SPL framing-anomaly queries flag the dual-header request and protocol-error response.

Test 3 Locate vulnerable Kestrel DLL on Windows host
windows

Find and read the file version of the Kestrel core assembly to confirm exposure.

Command

powershell
Get-ChildItem -Path 'C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App' -Recurse -Filter 'Microsoft.AspNetCore.Server.Kestrel.Core.dll' | ForEach-Object { $_.VersionInfo.FileVersion }

Cleanup

powershell
echo 'no cleanup required - read-only'

Expected Telemetry

DeviceFileEvents/FileWritten access to Kestrel DLL; PowerShell process execution reading file version.

Expected Detection

Endpoint inventory query (KQL/CQL) flags the DLL if its version is within the vulnerable ranges.

Related Detections