7.4
HIGH CVSS 3.1
CVE-2026-54784
CoreWCF: SPNEGO SecurityContextToken proof key wrapped without confidentiality
Description

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.

INFO

Published Date :

July 8, 2026, 11:16 p.m.

Last Modified :

July 8, 2026, 11:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-54784 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
Solution
Update CoreWCF to version 1.9.1 to fix impersonation and traffic manipulation vulnerabilities.
  • Update CoreWCF to version 1.9.1 or later.
  • Verify SPNEGO security configuration.
  • Monitor for impersonation attempts.
References to Advisories, Solutions, and Tools
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-54784 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-54784 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-54784 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-54784 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Jul. 08, 2026

    Action Type Old Value New Value
    Added Affected [{'vendor': 'CoreWCF', 'product': 'CoreWCF', 'versions': [{'status': 'affected', 'version': '>= 1.9.0, < 1.9.1'}]}]
    Added Description 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.
    Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
    Added CWE CWE-311
    Added CWE CWE-523
    Added Reference https://github.com/CoreWCF/CoreWCF/commit/2afae08b2fa5288428df89e8161116b816cf6b4b
    Added Reference https://github.com/CoreWCF/CoreWCF/commit/f216aa6929d41dc99cee098b1e69c260ec4c41c7
    Added Reference https://github.com/CoreWCF/CoreWCF/releases/tag/v1.9.1
    Added Reference https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-2288-8h3r-cqgg
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.