https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T10:23:00.008589+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-335485 EUVD-2026-335485 2026-10-06T10:23:00.056519+00:00 EUVD-2026-335485 https://cve.radiocsirt.org/vuln/fkie_cve-2026-54780 fkie_cve-2026-54780 2026-10-06T10:23:00.056557+00:00

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, the CoreWCF WS-Security 1.0 receive pipeline validates ds:SignedInfo SignatureMethod against the configured SecurityAlgorithmSuite but does not validate each ds:Reference DigestMethod, allowing a sender to use a rejected digest algorithm such as SHA-1 while the message is still accepted. This issue is fixed in versions 1.8.1 and 1.9.1.

 https://cve.radiocsirt.org/vuln/ghsa-4v55-cpmv-3vcm GHSA-4v55-cpmv-3vcm — CoreWCF: WS-Security Reference DigestMethod Algorithm-Suite Bypass 2026-10-06T10:23:00.056592+00:00

Affected: NuGet: CoreWCF.Primitives

### Impact 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.

### Patches Fixed in CoreWCF v1.8.1 and v1.9.1

### Workarounds None