Answer in brief
CVE-2026-54772 records a High severity (CVSS 7.5) vulnerability in CoreWCF: Pre-authentication infinite-loop CPU exhaustion in CoreWCF net.tcp / net.pipe / net.uds framing handshake. The current sources do not mark it as known exploited. The current feed maps CoreWCF/CoreWCF (generic), CoreWCF.NetFramingBase (nuget), CoreWCF.NetFramingBase (nuget). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps CoreWCF/CoreWCF (generic), CoreWCF.NetFramingBase (nuget), CoreWCF.NetFramingBase (nuget). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| CoreWCF/CoreWCFgeneric | >= 1.9.0, < 1.9.1 || < 1.8.1 | Not reported |
| CoreWCF.NetFramingBasenuget | <1.8.1 | 1.8.1 |
| CoreWCF.NetFramingBasenuget | >=1.9.0,<1.9.1 | 1.9.1 |
Published upstream
Jul 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.