Description
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.
References6
- github.com/CoreWCF/CoreWCF/commit/65d09022749854ba943e376aefb95…
- github.com/CoreWCF/CoreWCF/commit/b914495ce63c44924664643b60a26…
- github.com/CoreWCF/CoreWCF/commit/e7454132876ecc7e2cf80e541a443…
- github.com/CoreWCF/CoreWCF/releases/tag/v1.8.1
- github.com/CoreWCF/CoreWCF/releases/tag/v1.9.1
- github.com/CoreWCF/CoreWCF/security/advisories/GHSA-rpj7-hr7h-w…
Metrics
- CVSS 3.1
-
7.4
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N - EPSS — exploit probability
- 0% percentile: 10 · as of 15 November 2026
- CWE
- CWE-345CWE-347
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.