ASP.NET Core SignalR Redis Scale-Out Memory Leak Denial of Service
CVE-2026-114147 is a memory-release vulnerability in ASP.NET Core SignalR Redis scale-out. Case-mismatched group removal can leave subscriptions in a state that retains resources beyond their effective lifetime, permitting persistent resource amplification and memory exhaustion. An unauthenticated remote attacker can exploit this behavior to cause denial of service without user interaction. Affected runtime and standalone SignalR Redis packages span the 8.0, 9.0, 10.0, and 11.0 release lines.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can exhaust memory and disrupt the availability of affected ASP.NET Core applications through persistent resource amplification. The vulnerability has a CVSS v3.1 base score of 7.5, with high availability impact and no assessed confidentiality or integrity impact.
If you can’t patch tonight, do this now.
No vulnerability-specific temporary workaround is specified. Assess both the deployed runtime and the application's resolved SignalR Redis package version, including the bundled runtime in self-contained deployments, and prioritize patching affected applications.
Patch, then assume compromise.
Update both the ASP.NET Core runtime and the Microsoft.AspNetCore.SignalR.StackExchangeRedis package to the applicable patched release: 8.0.34, 9.0.23, 10.0.15, or 11.0.0. Restart framework-dependent applications after updating the runtime. Rebuild and redeploy applications after updating the standalone package; self-contained applications must also be rebuilt with the patched runtime. Updating only the machine-wide runtime or SDK does not update application-specific standalone package references. Distribution-managed installations should apply the corresponding vendor security updates.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
38 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.