CVE-2026-54784

HIGHPre-NVD 7.47.4
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.4 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:github_m
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 7.4Exploit: NoneExposed: 0

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

CoreWCF: SPNEGO SecurityContextToken proof key wrapped without confidentiality

Impact

When the proof key recovered from the RSTR can be observed by a party that is not the legitimate client, that party can impersonate the authenticated Windows principal for the lifetime of the SCT (default ~10 hours) and decrypt or forge any subsequent WS‑SecureConversation traffic that uses keys derived from the SCT.

Preconditions

Using security mode TransportWithMessageCredential with client credential type Windows, along with session establishment (which triggers use of WS-SecureConversation).

Patches

Fixed in CoreWCF v1.9.1

Workarounds

Ensure communication is protected by SSL/TLS to prevent capturing of SCT negotiation handshake.

CVSS v3
7.4
EG Score
7.4(low)
EPSS
—
KEV
Not listed

Published

June 19, 2026

Last Modified

June 19, 2026

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—

Data Freshness Timeline

(refreshed 15× in last 7d / 38× 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-07-06 22:25 UTCEG score recompute
  2. 2026-07-06 11:28 UTCEG score recompute
  3. 2026-07-06 00:36 UTCEG score recompute
  4. 2026-07-05 13:43 UTCEG score recompute
  5. 2026-07-05 02:49 UTCEG score recompute
  6. 2026-07-04 15:55 UTCEG score recompute
  7. 2026-07-04 05:02 UTCEG score recompute
  8. 2026-07-03 17:59 UTCEG score recompute
  9. 2026-07-03 07:03 UTCEG score recompute
  10. 2026-07-02 20:11 UTCEG score recompute
  11. 2026-07-02 09:16 UTCEG score recompute
  12. 2026-07-01 22:24 UTCEG score recompute
  13. 2026-07-01 11:03 UTCEG score recompute
  14. 2026-07-01 00:10 UTCEG score recompute
  15. 2026-06-30 13:16 UTCEG score recompute
  16. 2026-06-30 02:22 UTCEG score recompute
  17. 2026-06-29 15:29 UTCEG score recompute
  18. 2026-06-29 04:31 UTCEG score recompute
  19. 2026-06-28 17:37 UTCEG score recompute
  20. 2026-06-28 06:44 UTCEG score recompute
  21. 2026-06-27 19:52 UTCEG score recompute
  22. 2026-06-27 09:00 UTCEG score recompute
  23. 2026-06-26 22:06 UTCEG score recompute
  24. 2026-06-26 11:13 UTCEG score recompute
  25. 2026-06-25 19:15 UTCEG score recompute
Show 13 more
  1. 2026-06-25 08:22 UTCEG score recompute
  2. 2026-06-24 21:28 UTCEG score recompute
  3. 2026-06-24 10:35 UTCEG score recompute
  4. 2026-06-23 23:40 UTCEG score recompute
  5. 2026-06-23 12:46 UTCEG score recompute
  6. 2026-06-23 01:49 UTCEG score recompute
  7. 2026-06-22 14:57 UTCEG score recompute
  8. 2026-06-22 04:03 UTCEG score recompute
  9. 2026-06-21 17:08 UTCEG score recompute
  10. 2026-06-21 06:14 UTCEG score recompute
  11. 2026-06-20 19:21 UTCEG score recompute
  12. 2026-06-20 08:18 UTCEG score recompute
  13. 2026-06-19 21:25 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-54784?
CVE-2026-54784 is a high vulnerability published on June 19, 2026. CoreWCF: SPNEGO SecurityContextToken proof key wrapped without confidentiality Impact When the proof key recovered from the RSTR can be observed by a party that is not the legitimate client, that party can impersonate the authenticated Windows principal for the lifetime of the SCT (default ~10…
When was CVE-2026-54784 disclosed?
CVE-2026-54784 was first published in the National Vulnerability Database on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-54784?
CVE-2026-54784 has a CVSS v4.0 base score of 7.4 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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.

Start Free Scan →Browse All CVEs