Answer in brief
CVE-2026-54784 records a High severity (CVSS 7.4) vulnerability in CoreWCF: SPNEGO SecurityContextToken proof key wrapped without confidentiality. The current sources do not mark it as known exploited. The current feed maps CoreWCF/CoreWCF (generic), CoreWCF.Primitives (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.4. 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.Primitives (nuget). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| CoreWCF/CoreWCFgeneric | >= 1.9.0, < 1.9.1 | Not reported |
| CoreWCF.Primitivesnuget | >=1.9.0,<1.9.1 | 1.9.1 |
Published upstream
Jul 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 10, 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. In version 1.9.0, CoreWCF SPNEGO SecurityContextToken negotiation can expose the proof key recovered from the RSTR when TransportWithMessageCredential with Windows client credentials and session establishment are used, allowing an observer to impersonate the authenticated Windows principal and decrypt or forge WS-SecureConversation traffic. This issue is fixed in version 1.9.1.
Quoted source text, attributed separately from HOL analysis.