CVE-2026-54772 CoreWCF: Pre-authentication infinite-loop CPU exhaustion in CoreWCF net.tcp / net.pipe / net.uds framing handshake
Unauthenticated attackers can cause CPU exhaustion and denial of service in CoreWCF applications by triggering infinite loops during network framing handshakes.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-54772?
CVE-2026-54772 is a high-severity denial of service vulnerability in CoreWCF, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. Prior to 1.8.1 and 1.9.1, an unauthenticated remote attacker that can reach a NetTcpBinding, NetNamedPipeBinding, or UnixDomainSocketBinding endpoint can trigger premature EOF handling in the CoreWCF net.tcp, net.pipe, or net.uds framing handshake and pin one server thread-pool worker at full CPU per connection. This issue is fixed in versions 1.8.1 and 1.9.1.
Which versions are affected by CVE-2026-54772?
4 open source packages ship an affected version, including CoreWCF.NetFramingBase.
| Package | Affected | Fixed in |
|---|---|---|
CoreWCF.NetFramingBase NuGet | All versions | 1.8.1 |
CoreWCF.NetFramingBase NuGet | All versions | 1.8.1 |
CoreWCF.NetFramingBase NuGet | From 1.9.0 | 1.9.1 |
CoreWCF.NetFramingBase NuGet | From 1.9.0 | 1.9.1 |
How do I fix CVE-2026-54772?
Upgrade CoreWCF.NetFramingBase to a fixed version for your release line: 1.8.1 or 1.9.1.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-54772 being exploited?
There is no known exploitation of CVE-2026-54772 in the wild and no public exploit code.
Sources
Also known as GHSA-p86g-xrr2-pf7c.