CVE-2026-54774

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 90% 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.2%CVSS: 7.4Exploit: 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, SamlSerializer skips final SignatureValue verification when a CoreWCF service validates SAML tokens using a non-X.509 signing token, allowing an attacker to reference a non-X.509 SecurityToken key identifier and bypass assertion signature verification. This issue is fixed in versions 1.8.1 and 1.9.1.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

Published

June 19, 2026

Last Modified

July 10, 2026

Advisory Details (6)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_release, github.
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 e7454132876e (CoreWCF/CoreWCF)

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

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

commit b914495ce63c (CoreWCF/CoreWCF)

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

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

commit 65d090227498 (CoreWCF/CoreWCF)

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

https://github.com/CoreWCF/CoreWCF/commit/65d09022749854ba943e376aefb958dec05b00d8
githubMentions a patch (unverified)

SamlSerializer skips SignatureValue verification when SAML signing token is not an X.509 certificate · Advisory · CoreWCF/CoreWCF · GitHub

https://github.com/CoreWCF/CoreWCF/security/advisories/GHSA-rpj7-hr7h-w6p9

Vendor Advisories for CVE-2026-54774(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 113 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 04: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:08 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:47 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 02:21 UTCEG score recompute
  15. 2026-08-24 14:00 UTCEG score recompute
  16. 2026-08-23 11:59 UTCEG score recompute
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-22 23:39 UTCEG score recompute
  19. 2026-08-21 23:49 UTCEPSS rescore
  20. 2026-08-21 08:42 UTCEG score recompute
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 07:59 UTCEG score recompute
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 07:00 UTCEG score recompute
  25. 2026-08-18 13:48 UTCEPSS rescore
  26. 2026-08-17 13:47 UTCEPSS rescore
  27. 2026-08-17 01:01 UTCEG score recompute
  28. 2026-08-16 14:56 UTCEPSS rescore
  29. 2026-08-16 12:41 UTCEG score recompute
  30. 2026-08-16 02:14 UTCEPSS rescore
  31. 2026-08-15 12:01 UTCEG score recompute
  32. 2026-08-15 01:30 UTCEPSS rescore
  33. 2026-08-13 23:02 UTCEG score recompute
  34. 2026-08-13 22:00 UTCEPSS rescore
  35. 2026-08-12 22:24 UTCEG score recompute
  36. 2026-08-12 13:51 UTCEPSS rescore
  37. 2026-08-11 21:44 UTCEG score recompute
  38. 2026-08-11 09:25 UTCEG score recompute
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-09 20:22 UTCEG score recompute
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-08 19:44 UTCEG score recompute
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-06 18:25 UTCEG score recompute
  45. 2026-08-06 13:47 UTCEPSS rescore
  46. 2026-08-06 06:06 UTCEG score recompute
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-04 15:19 UTCEG score recompute
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:39 UTCEPSS rescore
  51. 2026-08-03 14:20 UTCEG score recompute
  52. 2026-08-03 10:36 UTCEPSS rescore
  53. 2026-08-02 13:17 UTCEG score recompute
  54. 2026-08-02 02:27 UTCEPSS rescore
  55. 2026-08-01 12:37 UTCEG score recompute
  56. 2026-08-01 04:16 UTCEPSS rescore
  57. 2026-07-30 22:18 UTCEG score recompute
  58. 2026-07-30 16:28 UTCEPSS rescore
  59. 2026-07-30 02:54 UTCEG score recompute
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-29 01:34 UTCEG score recompute
  62. 2026-07-28 15:37 UTCEPSS rescore
  63. 2026-07-27 21:20 UTCEG score recompute
  64. 2026-07-26 16:48 UTCEG score recompute
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-24 14:18 UTCEPSS rescore
  67. 2026-07-23 14:18 UTCEPSS rescore
  68. 2026-07-23 03:19 UTCEG score recompute
  69. 2026-07-22 14:08 UTCEPSS rescore
  70. 2026-07-21 15:25 UTCEPSS rescore
  71. 2026-07-20 17:08 UTCEPSS rescore
  72. 2026-07-19 14:31 UTCEPSS rescore
  73. 2026-07-19 14:31 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-16 17:03 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-54774?
CVE-2026-54774 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. Prior to 1.8.1 and 1.9.1, SamlSerializer skips final SignatureValue verification when a CoreWCF service validates SAML tokens using a non-X.509 signing token, allowing an attacker to reference a non-X.509…
When was CVE-2026-54774 disclosed?
CVE-2026-54774 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-54774 actively exploited?
CVE-2026-54774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54774?
CVE-2026-54774 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54774?
A fix for CVE-2026-54774 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54774 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-54774

Explore →

Is Your Infrastructure Affected by CVE-2026-54774?

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

Book a Demo →Browse All CVEs