Quick answers
- Is CVE-2026-114147 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-114147 being exploited in the wild.
- How severe is CVE-2026-114147?
- High severity, with a CVSS score of 7.5, published 10 November 2026.
- Which products and versions are affected?
- Microsoft.AspNetCore.App.Runtime.linux-arm (NuGet) >= 8.0.0-preview.1.23112.2, <= 8.0.33; Microsoft.AspNetCore.App.Runtime.linux-arm64 (NuGet) >= 8.0.0-preview.1.23112.2, <= 8.0.33; Microsoft.AspNetCore.App.Runtime.linux-musl-arm (NuGet) >= 8.0.0-preview.1.23112.2, <= 8.0.33; Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 (NuGet) >= 8.0.0-preview.1.23112.2, <= 8.0.33; and 8 more.
- Is there a fix for CVE-2026-114147?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-114147 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-114147?
- Check whether you run Microsoft Asp.Net Core, Microsoft.AspNetCore.App.Runtime.linux-arm (NuGet), Microsoft.AspNetCore.App.Runtime.linux-arm64 (NuGet) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A memory release issue in ASP.NET Core allows an attacker to send network requests that trigger memory leaks, gradually exhausting the application's memory resources. The vulnerability requires network access but no authentication, and can lead to denial of service through memory exhaustion or process termination.
Affected products
- Microsoft ASP.NET Core
Identifiers
- CVE-2026-114147
- GHSA-wr8v-9x5q-ggcm
Timeline
- 2026-11-10: disclosed