CVE-2026-54782

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% 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
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. Prior to 1.8.1 and 1.9.1, CoreWCF SAML 1.1 and SAML 2.0 token validation does not correctly resolve the issuer signing key or require signed tokens when IdentityConfiguration is used with federated bindings, allowing an unauthenticated remote attacker to impersonate any principal the trusted STS could issue. This issue is fixed in versions 1.8.1 and 1.9.1.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
60
EG Risk 60/100

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
Severity100% × 45%
Exploitation0% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

Published

June 19, 2026

Last Modified

July 10, 2026

Advisory Details (6)

Auto-updated Oct 3, 2026
Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)

Authentication bypass in CoreWCF SAML 1.1 / 2.0 token signature validation · Advisory · CoreWCF/CoreWCF · GitHub

https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-xjr9-gg9q-jx3v
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_release Patch Available

CoreWCF v1.8.1

Patch available: CoreWCF/CoreWCF v1.8.1

https://github.com/CoreWCF/CoreWCF/releases/tag/v1.8.1
github_commit Patch Available

commit e5cc9b6a4ecc (CoreWCF/CoreWCF)

Patch available: CoreWCF/CoreWCF v1.8.1 (contains commit e5cc9b6a4ecc)

https://github.com/CoreWCF/CoreWCF/commit/e5cc9b6a4ecc102a50d782093bfc72e0790abe3d
github_commit

commit 0e63c2cca557 (CoreWCF/CoreWCF)

Fix landed in CoreWCF/CoreWCF commit 0e63c2cca557 — awaiting tagged release

https://github.com/CoreWCF/CoreWCF/commit/0e63c2cca55763d8be6b226a234579280a09e7b6
github_commit Patch Available

commit 0b8c8af85126 (CoreWCF/CoreWCF)

Patch available: CoreWCF/CoreWCF v1.9.1 (contains commit 0b8c8af85126)

https://github.com/CoreWCF/CoreWCF/commit/0b8c8af851260e85e8402af53233d1b8f87dfb6f

Vendor Advisories for CVE-2026-54782(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 rangeFix by version rangeDependents
CoreWCF.Primitives1.9.0
  • every version up to 1.8.1: fixed in 1.8.1
  • 1.9.0 up to 1.9.1: fixed in 1.9.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 26× 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.

Showing the most recent 100 of 118 total refreshes for this CVE.

  1. 2026-10-06 15:18 UTCEPSS rescore
  2. 2026-10-05 17:43 UTCEPSS rescore
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 13:39 UTCOSV refresh
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 15:22 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-24 14:04 UTCEPSS rescore
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-20 20:16 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-17 19:31 UTCEPSS rescore
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-15 03:11 UTCEPSS rescore
  21. 2026-09-14 02:13 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-13 13:07 UTCEG score recompute
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 75 more
  1. 2026-09-08 22:01 UTCEPSS rescore
  2. 2026-09-07 16:01 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:12 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 20:46 UTCEG score recompute
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-24 22:17 UTCEG score recompute
  16. 2026-08-24 14:00 UTCEG score recompute
  17. 2026-08-23 03:40 UTCEG score recompute
  18. 2026-08-23 00:19 UTCEPSS rescore
  19. 2026-08-22 23:39 UTCEG score recompute
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 00:21 UTCEG score recompute
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 07:59 UTCEG score recompute
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-19 07:00 UTCEG score recompute
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-17 17:08 UTCEG score recompute
  28. 2026-08-17 13:47 UTCEPSS rescore
  29. 2026-08-16 16:52 UTCEG score recompute
  30. 2026-08-16 14:56 UTCEPSS rescore
  31. 2026-08-16 04:58 UTCEG score recompute
  32. 2026-08-16 02:14 UTCEPSS rescore
  33. 2026-08-15 02:38 UTCEG score recompute
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-13 22:48 UTCEG score recompute
  36. 2026-08-13 22:00 UTCEPSS rescore
  37. 2026-08-12 17:18 UTCEG score recompute
  38. 2026-08-12 13:51 UTCEPSS rescore
  39. 2026-08-11 17:29 UTCEG score recompute
  40. 2026-08-11 01:23 UTCEG score recompute
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-09 17:22 UTCEG score recompute
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-08 17:34 UTCEG score recompute
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-07 17:46 UTCEG score recompute
  47. 2026-08-06 14:00 UTCEG score recompute
  48. 2026-08-06 13:47 UTCEPSS rescore
  49. 2026-08-05 21:45 UTCEG score recompute
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 15:19 UTCEG score recompute
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 10:39 UTCEPSS rescore
  54. 2026-08-03 14:20 UTCEG score recompute
  55. 2026-08-03 10:36 UTCEPSS rescore
  56. 2026-08-02 04:49 UTCEG score recompute
  57. 2026-08-02 02:27 UTCEPSS rescore
  58. 2026-08-01 05:01 UTCEG score recompute
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-30 22:18 UTCEG score recompute
  61. 2026-07-30 16:28 UTCEPSS rescore
  62. 2026-07-30 02:54 UTCEG score recompute
  63. 2026-07-30 01:30 UTCEPSS rescore
  64. 2026-07-29 01:33 UTCEG score recompute
  65. 2026-07-28 15:37 UTCEPSS rescore
  66. 2026-07-27 18:02 UTCEG score recompute
  67. 2026-07-26 16:47 UTCEG score recompute
  68. 2026-07-26 14:54 UTCEPSS rescore
  69. 2026-07-25 14:18 UTCEPSS rescore
  70. 2026-07-24 14:18 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 03:19 UTCEG score recompute
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-21 15:25 UTCEPSS rescore
  75. 2026-07-20 17:08 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54782?
CVE-2026-54782 is a critical vulnerability published on June 19, 2026. CoreWCF is a port of the service side of Windows Communication Foundation (WCF) to .NET Core. Prior to 1.8.1 and 1.9.1, CoreWCF SAML 1.1 and SAML 2.0 token validation does not correctly resolve the issuer signing key or require signed tokens when IdentityConfiguration is used with federated…
When was CVE-2026-54782 disclosed?
CVE-2026-54782 was first published 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-54782 actively exploited?
CVE-2026-54782 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54782?
CVE-2026-54782 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54782?
A fix for CVE-2026-54782 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54782 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54782?

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

Book a Demo →Browse All CVEs