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-54773
CoreWCF: WS-Security signature substitution via document-wide Signature lookup
Impact
An unauthenticated remote attacker who can place a SOAP header lexically before wsse:Security can embed a ds:Signature of their choosing inside that header and cause the server to verify the attacker-supplied signature instead of the one carried in the security header.
Preconditions
Exploitation requires the endpoint be configured with an endorsing supporting token binding, and the attacker constructs a ds:Signature whose KeyInfo resolves through the receive-side token resolver to a key under the attacker’s control. Both are conditions outside the attacker’s direct control on a generic deployment.
Patches
Fixed in CoreWCF v1.8.1 and v1.9.1
Workarounds
Use a security token resolver that only accepts references to issuer-pinned X.509 chains (the default when expecting a static set of signing certificates).
Medium Basis: The source's own band: MODERATE
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