cve.bz

CVE-2026-54784 corewcf corewcf: Missing Encryption of Sensitive Data

7.4 highEPSS 0.3%Fix available

High (7.4) in corewcf corewcf. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in CoreWCF.Primitives 1.9.1.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-311 Missing Encryption of Sensitive Data
CWE-523 Unprotected Transport of Credentials
OWASP Top 10
A04:2025 Cryptographic Failures, A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • CoreWCF.Primitives (NuGet): fixed in 1.9.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-54784 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54784?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54784?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54784 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
CoreWCF>= 1.9.0, < 1.9.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2288-8h3r-cqggNuGetCoreWCF.Primitives>=1.9.0 <1.9.11.9.1

Attack patterns (CAPEC)

  • CAPEC-102 Session Sidejacking Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-311 (14).

References

Check your stackJSON