CVE-2025-55315: CVE-2025-55315: Inconsistent interpretation of http requests ('http request/response smuggling') in ASP.NE…
microsoft · asp.net core · NVD published 2025-10-14 · posted 2025-10-16 · last modified 2026-10-19
What it is
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.
| Weakness | CWE-444 |
|---|---|
| CVSS vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L (source: [email protected]) |
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2025-10-16 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
Exploit-DB
- EDB-52492: ASP.net 8.0.10 - Bypass (2026-04-06)
GitHub proof-of-concept repositories
7 public repositories from 7 accounts, first seen 2025-10-16. Most starred: sirredbeard/CVE-2025-55315-repro (46 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: Exploit-DB (OffSec) · nomi-sec/PoC-in-GitHub.
No ATT&CK techniques could be mapped or inferred for this CVE yet.
How to fix it
Fixed versions
- microsoft asp.net core: upgrade to 2.3.6 or later (affected from 2.3.0)
- microsoft asp.net core: upgrade to 8.0.21 or later (affected from 8.0.0)
- microsoft asp.net core: upgrade to 9.0.10 or later (affected from 9.0.0)
- microsoft visual studio 2022: upgrade to 17.10.20 or later (affected from 17.10.0)
- microsoft visual studio 2022: upgrade to 17.12.13 or later (affected from 17.12.10)
- microsoft visual studio 2022: upgrade to 17.14.17 or later (affected from 17.14.0)
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55315 (Vendor Advisory)
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.