CVE-2025-36854
BaseFortify
Publication date: 2025-09-08
Last updated on: 2025-09-08
Assigner: HeroDevs
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| microsoft | asp.net_core | 8.0.0 |
| microsoft | asp.net_core | 6.0.0 |
| microsoft | asp.net_core | 8.0.8 |
| microsoft | asp.net_core | 9.0.0-preview.1.24081.5 |
| microsoft | asp.net_core | 9.0.0.rc.1 |
| microsoft | asp.net_core | 6.0.36 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free issue in ASP.NET Core Runtime when closing an HTTP/3 stream while application code is writing to the response body. A race condition may occur, causing the application to reference memory that has already been freed, which can lead to remote code execution. It affects certain versions of ASP.NET Core, including 6.0.0 through 6.0.36, 8.0.0 through 8.0.8, and 9.0.0-preview.1.24081.5 through 9.0.0.RC.1, including self-contained applications targeting these versions. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to execute arbitrary code remotely on the affected system by exploiting the use-after-free condition during HTTP/3 stream handling. This can lead to full compromise of the affected application or server, potentially resulting in data breaches, service disruption, or unauthorized access. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade to patched versions of the ASP.NET Core Runtime: version 8.0.10 or later, 9.0.0.RC2 or later, or corresponding .NET SDK versions. If you are using ASP.NET Core 6.x, which is end-of-life, consider migrating to supported versions or using commercial support such as HeroDevs' Never-Ending Support (NES) offering. Additionally, if you have deployed self-contained applications targeting affected versions, recompile and redeploy them with the patched runtime versions. [1]