Skip to main content
CVE-2025-55315VulnerabilityPublished Updated

CVE-2025-55315: Microsoft ASP.NET Core 2.3 · HTTP Request/Response Smuggling

Affects Microsoft ASP.NET Core 2.3Source CVE Database V5

0

Not known to be exploited · public exploit available (Exploit-DB) · 66% EPSS · CVSS 9.9 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
66.5% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L/E:U/RL:O/RC:C

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 14 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by microsoft

    , 63 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 17 minutes after disclosure

  4. , 174 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Microsoft ASP.NET Core 2.3Affected
  • =2.3
Fixed in–

AI-suggested

To mitigate CVE-2025-55315, organizations should prioritize upgrading from ASP.NET Core 2.3 to a later, patched version as soon as a fix becomes available from Microsoft. In the interim, implement strict HTTP input validation and sanitization at both application and web server levels to detect and block malformed or suspicious HTTP requests indicative of request smuggling attempts. Deploy Web Application Firewalls (WAFs) with updated rulesets capable of identifying and mitigating HTTP request smuggling patterns. Network segmentation and limiting access to web application endpoints to trusted networks can reduce exposure. Monitor HTTP traffic logs for anomalies such as unexpected header sequences or irregular request lengths. Employ layered security controls including intrusion detection systems (IDS) and anomaly detection tools to identify potential exploitation attempts. Conduct regular security assessments and penetration testing focused on HTTP request handling. Educate development and security teams about the risks of HTTP request smuggling and ensure secure coding practices are followed to prevent similar issues. Finally, maintain an incident response plan tailored to web application attacks to enable rapid containment if exploitation is detected.

Description

Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NET Core allows an authorized attacker to bypass a security feature over a network.

Reports on CVE-2025-55315

References

Community reviews

Loading reviews…