CVE-2025-55315

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 1.7%, top 18% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.9
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 66%
CISA-KEV: Not listedEPSS: 66%CVSS: 9.9Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
9.9
EG Score
9.9(medium)
EPSS
99.2%
KEV
Not listed

Published

October 14, 2025

Last Modified

October 28, 2025

Advisory Details (3)

Auto-updated Jul 20, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft.
generic🟡 PoC Available

Kestrel Chunked Smuggling Proof of Concept (CVE-2025-55315) · GitHub

https://gist.github.com/N3mes1s/d0897c13ca199e739ecc2b562f466040
generic🔴 Active Exploitation

Understanding the worst .NET vulnerability ever: request smuggling and CVE-2025-55315

https://andrewlock.net/understanding-the-worst-dotnet-vulnerability-request-smuggling-and-cve-2025-55315/
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-55315

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunetstandard-targeting-pack-2.1-8.0 (8.0.121-0ubuntu1~22.04.1) @ jammy2026-05-29ubuntu
redhatdotnet9-0-main-9.0.116-1.hum12026-04-21redhat
redhatdotnet8-0-main-8.0.126-1.hum12026-04-20redhat
redhatdevspaces/udi-rhel9:3.25.0-17655822072025-12-15redhat
redhatdotnet10.0-0:10.0.100~rc.2.25502.107-0.10.el9_72025-11-11redhat
redhatdotnet10.0-0:10.0.100~rc.2.25502.107-0.12.el10_12025-11-11redhat
redhatdotnet8.0-0:8.0.121-1.el9_42025-10-16redhat
redhatdotnet9.0-0:9.0.111-1.el8_102025-10-15redhat
redhatdotnet8.0-0:8.0.121-1.el9_62025-10-15redhat
redhatdotnet9.0-0:9.0.111-1.el10_02025-10-15redhat
redhatdotnet8.0-0:8.0.121-1.el8_102025-10-15redhat
redhatdotnet9.0-0:9.0.111-1.el9_62025-10-15redhat
redhatdotnet8.0-0:8.0.121-1.el10_02025-10-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(13 across 1 ecosystem)
NuGet(13)
PackageVulnerable rangeFixed inDependents
Microsoft.AspNetCore.App.Runtime.linux-arm8.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.linux-arm648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.linux-musl-arm8.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.linux-musl-arm648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.linux-musl-x648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.linux-x648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.osx-arm648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.osx-x648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.win-arm8.0.21
Microsoft.AspNetCore.App.Runtime.win-arm648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.win-x648.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.App.Runtime.win-x868.0.0 ... 8.0.8 (20 versions)8.0.21
Microsoft.AspNetCore.Server.Kestrel.Core0.0.1-alpha ... 2.3.0 (22 versions)2.3.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 7× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 01:59 UTCEPSS rescore
  11. 2026-07-15 01:59 UTCEPSS rescore
  12. 2026-07-13 22:29 UTCEPSS rescore
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-11 08:27 UTCEPSS rescore
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-09 19:09 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 12:11 UTCOSV refresh
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-02 17:01 UTCEPSS rescore
  22. 2026-07-01 15:06 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 45 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-24 14:04 UTCEPSS rescore
  3. 2026-06-24 14:04 UTCEPSS rescore
  4. 2026-06-23 21:32 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 00:05 UTCOSV refresh
  10. 2026-06-17 17:52 UTCEPSS rescore
  11. 2026-06-16 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:48 UTCEPSS rescore
  14. 2026-06-14 23:17 UTCEPSS rescore
  15. 2026-06-13 23:00 UTCEPSS rescore
  16. 2026-06-12 23:11 UTCEPSS rescore
  17. 2026-06-11 14:00 UTCEPSS rescore
  18. 2026-06-11 14:00 UTCEPSS rescore
  19. 2026-06-10 22:18 UTCEPSS rescore
  20. 2026-06-10 22:18 UTCEPSS rescore
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-08 14:16 UTCEPSS rescore
  24. 2026-06-08 14:16 UTCEPSS rescore
  25. 2026-06-07 15:24 UTCEPSS rescore
  26. 2026-06-07 15:24 UTCEPSS rescore
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-06 13:47 UTCEPSS rescore
  29. 2026-06-05 22:46 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 06:10 UTCEPSS rescore
  32. 2026-06-05 06:10 UTCEPSS rescore
  33. 2026-06-04 13:12 UTCEPSS rescore
  34. 2026-06-04 13:12 UTCEPSS rescore
  35. 2026-06-02 20:12 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-05-31 22:30 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 00:16 UTCEPSS rescore
  42. 2026-05-31 00:16 UTCEPSS rescore
  43. 2026-05-29 20:53 UTCEG score recompute
  44. 2026-05-29 20:53 UTCVendor advisory
  45. 2026-05-29 13:44 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52492
    First seen Apr 6, 2026

    ASP.net 8.0.10 - Bypass

    Open source ↗
  • GitHub PoCZemarKhos/CVE-2025-55315-PoC-Exploit
    First seen Nov 11, 2025

    CVE-2025-55315 PoC Exploit

    Open source ↗
  • GitHub PoCsirredbeard/CVE-2025-55315-repro
    First seen Oct 16, 2025

    Tool that reproduces CVE-2025-55315 in ASP.NET Core.

    Open source ↗

Frequently asked(5)

What is CVE-2025-55315?
CVE-2025-55315 is a critical vulnerability published on October 14, 2025. 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.
When was CVE-2025-55315 disclosed?
CVE-2025-55315 was first published in the National Vulnerability Database on October 14, 2025, with the most recent update on October 28, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-55315 actively exploited?
CVE-2025-55315 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-55315?
CVE-2025-55315 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-55315?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-55315, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-55315

Explore →

Is Your Infrastructure Affected by CVE-2025-55315?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.