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 WS-Security signature verification performs a document-wide ds:Signature lookup, allowing an unauthenticated remote attacker to place a SOAP header before wsse:Security and cause WSSecurityOneDotZeroReceiveSecurityHeader to verify an attacker-supplied signature instead of the security header signature. This issue is fixed in versions 1.8.1 and 1.9.1.
References6
- github.com/CoreWCF/CoreWCF/commit/0589692d4b9a41d21b34ac48281e9…
- github.com/CoreWCF/CoreWCF/commit/30aef805270976c42477e3f2a05f4…
- github.com/CoreWCF/CoreWCF/commit/4618f24165ad018ad3ed2636bf8c3…
- 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-jc6x-rj79-w…
Metrics
- CVSS 3.1
-
5.9
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N - EPSS — exploit probability
- 0% percentile: 31 · as of 15 November 2026
- CWE
- CWE-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.