CoreWCF.Primitives
Affected
- introduced
0, fixed1.8.1(ecosystem)
Fixed versions
1.8.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-54781
CoreWCF: SAML SubjectConfirmation methods and holder-of-key proof keys are not enforced
Impact
The relying application is given a ClaimsPrincipal for a subject whose authority over the assertion the sender never proved. There are two distinct exploit shapes:
Preconditions
The service is configured to accept SAML 1.1 tokens via federation. Typical bindings are WS2007FederationHttpBinding and WSFederationHttpBinding, or any custom binding using IssuedSecurityTokenParameters with a SAML 1.1 token type.
The attacker has obtained at least one signed SAML 1.1 assertion of a shape that triggers the bypass.
Patches
Fixed in CoreWCF v1.8.1 and v1.9.1
Workarounds
To exploit this issue, it's required that a trusted STS issues SAML assertions whose SubjectConfirmationMethod is not one of the SAML 1.1 trio, or is willing to issue holder-of-key assertions without KeyInfo. If no trusted STS is willing to issue SAML assertions meeting either of these criteria, then a service isn't vulnerable.
High Basis: The source's own band: HIGH
0, fixed 1.8.1 (ecosystem)1.8.1
The export has no generic command for this ecosystem.
1.9.0, fixed 1.9.1 (ecosystem)1.9.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0