CoreWCF’s WS-Security 1.0 receive pipeline validates the SignatureMethod of an incoming ds:SignedInfo against the configured SecurityAlgorithmSuite, but does not validate the DigestMethod declared on each ds:Reference. As a result, a sender can populate ds:SignedInfo with SignatureMethod values the suite accepts (for example rsa-sha256 under Basic256Sha256) while declaring a per-reference DigestMethod the suite rejects (for example http://www.w3.org/2000/09/xmldsig#sha1). The signature is then verified where it permits SHA-1 digests, and the message is accepted.
Fixed in CoreWCF v1.8.1 and v1.9.1
None
{
"nvd_published_at": null,
"github_reviewed_at": "2026-06-19T20:47:04Z",
"github_reviewed": true,
"severity": "LOW",
"cwe_ids": [
"CWE-327",
"CWE-757"
]
}