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, 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.
References6
- github.com/CoreWCF/CoreWCF/commit/0b8c8af851260e85e8402af53233d…
- github.com/CoreWCF/CoreWCF/commit/0e63c2cca55763d8be6b226a23457…
- github.com/CoreWCF/CoreWCF/commit/e5cc9b6a4ecc102a50d782093bfc7…
- 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-xjr9-gg9q-j…
Metrics
- CVSS 3.1
-
10.0
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N - EPSS — exploit probability
- 0% percentile: 36 · as of 15 November 2026
- CWE
- CWE-290CWE-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.