CVE-2026-54784

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

June 19, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

CoreWCF v1.9.1

Patch available: CoreWCF/CoreWCF v1.9.1

https://github.com/CoreWCF/CoreWCF/releases/tag/v1.9.1
github_commit

commit f216aa6929d4 (CoreWCF/CoreWCF)

Fix landed in CoreWCF/CoreWCF commit f216aa6929d4 — awaiting tagged release

https://github.com/CoreWCF/CoreWCF/commit/f216aa6929d41dc99cee098b1e69c260ec4c41c7
github_commit Patch Available

commit 2afae08b2fa5 (CoreWCF/CoreWCF)

Patch available: CoreWCF/CoreWCF v1.9.1 (contains commit 2afae08b2fa5)

https://github.com/CoreWCF/CoreWCF/commit/2afae08b2fa5288428df89e8161116b816cf6b4b
github Patch Available

SPNEGO SecurityContextToken proof key wrapped without confidentiality · Advisory · CoreWCF/CoreWCF · GitHub

https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-2288-8h3r-cqgg

Vendor Advisories for CVE-2026-54784(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
CoreWCF.Primitives1.9.01.9.1

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-23 10:31 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-22 23:38 UTCEG score recompute
  4. 2026-08-21 23:49 UTCEPSS rescore
  5. 2026-08-21 05:50 UTCEG score recompute
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 07:59 UTCEG score recompute
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 07:00 UTCEG score recompute
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 20:24 UTCEG score recompute
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 06:36 UTCEG score recompute
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 08:51 UTCEG score recompute
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-13 22:52 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 14:13 UTCEG score recompute
  21. 2026-08-12 13:51 UTCEPSS rescore
  22. 2026-08-11 16:28 UTCEG score recompute
  23. 2026-08-11 05:36 UTCEG score recompute
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-09 20:18 UTCEG score recompute
Show 51 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-08 22:33 UTCEG score recompute
  3. 2026-08-08 16:37 UTCEPSS rescore
  4. 2026-08-08 00:45 UTCEG score recompute
  5. 2026-08-06 15:59 UTCEG score recompute
  6. 2026-08-06 13:47 UTCEPSS rescore
  7. 2026-08-06 04:39 UTCEG score recompute
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 15:19 UTCEG score recompute
  10. 2026-08-04 15:10 UTCEPSS rescore
  11. 2026-08-04 10:39 UTCEPSS rescore
  12. 2026-08-03 14:20 UTCEG score recompute
  13. 2026-08-03 10:36 UTCEPSS rescore
  14. 2026-08-02 05:35 UTCEG score recompute
  15. 2026-08-02 02:27 UTCEPSS rescore
  16. 2026-08-01 07:50 UTCEG score recompute
  17. 2026-08-01 04:16 UTCEPSS rescore
  18. 2026-07-30 22:18 UTCEG score recompute
  19. 2026-07-30 16:28 UTCEPSS rescore
  20. 2026-07-30 02:54 UTCEG score recompute
  21. 2026-07-30 01:30 UTCEPSS rescore
  22. 2026-07-29 01:33 UTCEG score recompute
  23. 2026-07-28 15:37 UTCEPSS rescore
  24. 2026-07-27 18:02 UTCEG score recompute
  25. 2026-07-26 16:47 UTCEG score recompute
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-24 14:18 UTCEPSS rescore
  29. 2026-07-23 14:18 UTCEPSS rescore
  30. 2026-07-23 03:19 UTCEG score recompute
  31. 2026-07-22 14:08 UTCEPSS rescore
  32. 2026-07-21 15:25 UTCEPSS rescore
  33. 2026-07-20 17:08 UTCEPSS rescore
  34. 2026-07-19 14:31 UTCEPSS rescore
  35. 2026-07-19 14:31 UTCEPSS rescore
  36. 2026-07-19 02:29 UTCEPSS rescore
  37. 2026-07-18 10:04 UTCEPSS rescore
  38. 2026-07-16 17:03 UTCEPSS rescore
  39. 2026-07-15 16:57 UTCEPSS rescore
  40. 2026-07-15 16:57 UTCEPSS rescore
  41. 2026-07-15 02:00 UTCEPSS rescore
  42. 2026-07-15 02:00 UTCEPSS rescore
  43. 2026-07-13 22:31 UTCEPSS rescore
  44. 2026-07-13 06:13 UTCEPSS rescore
  45. 2026-07-13 06:13 UTCEPSS rescore
  46. 2026-07-12 05:46 UTCEPSS rescore
  47. 2026-07-11 08:27 UTCEPSS rescore
  48. 2026-07-11 08:27 UTCEPSS rescore
  49. 2026-07-09 19:10 UTCEPSS rescore
  50. 2026-07-09 19:10 UTCEPSS rescore
  51. 2026-06-19 21:25 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-54784?
CVE-2026-54784 is a high vulnerability published on June 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…
When was CVE-2026-54784 disclosed?
CVE-2026-54784 was first published in the National Vulnerability Database on June 19, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54784 actively exploited?
CVE-2026-54784 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54784?
CVE-2026-54784 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-54784?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54784, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54784

Explore →

Is Your Infrastructure Affected by CVE-2026-54784?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.