CVE-2026-54779 json
CoreWCF: SAML token replay protection is inoperative
published 2026-06-19 4 mo ago modified 2026-07-09 4 mo ago also EUVD-2026-42463 , GHSA-9jr3-rj99-8jq3
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
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 token replay protection is inoperative because DefaultTokenReplayCache.TryAdd does not reject duplicate tokens when DetectReplayedTokens is enabled, allowing a captured token to be reused. This issue is fixed in versions 1.8.1 and 1.9.1.
Patch / fix
- nuget CoreWCF.Primitives 1.8.1, 1.9.1
- corewcf corewcf 1.8.1, 1.9.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| nuget | CoreWCF.Primitives | <1.8.1 >=1.9.0, <1.9.1 |
1.8.1 1.9.1 |
Affected products
- CoreWCF CoreWCF
Classification
References
- github.com /CoreWCF/CoreWCF/commit/3800c4e2bb4c6fde00ddacefdc2221ef33d55621
- github.com /CoreWCF/CoreWCF/commit/7b0b5231cf21b4b5c1fc3caac9981f8bee43823f
- github.com /CoreWCF/CoreWCF/commit/84f8cff5a786b5aaa73448cb379d366a7df98238
-
github.com
/CoreWCF/CoreWCF/security/advisories/GHSA-9jr3-rj99-8jq3
web
- github.com /CoreWCF/CoreWCF/releases/tag/v1.8.1
- github.com /CoreWCF/CoreWCF/releases/tag/v1.9.1
-
github.com
/CoreWCF/CoreWCF
package
Sources
- CVE List CVE-2026-54779
- GitHub Advisory GHSA-9jr3-rj99-8jq3
- NVD CVE-2026-54779
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.