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 endorsing and supporting signature verification does not ensure the selected ds:Signature covers the expected Security header target, allowing an attacker with one captured signed SOAP envelope to replay arbitrary service operations as the victim principal. This issue is fixed in versions 1.8.1 and 1.9.1.
Published: 2026-07-08
Score: 7.4 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

CoreWCF is a .NET Core version of Windows Communication Foundation’s service side. Prior to releases 1.8.1 and 1.9.1, its WS‑Security endorsement and support signature verification omitted a check that ensures the selected ds:Signature references the intended Security header, enabling an XML Signature Wrapping attack. An adversary who captures a legitimate signed SOAP envelope can replay it to execute arbitrary service operations as the victim’s identity. The vulnerability is resolved in CoreWCF 1.8.1 and 1.9.1.

Affected Systems

The issue affects the CoreWCF product for .NET Core. Versions prior to 1.8.1 and 1.9.1 are vulnerable. The fix is available in CoreWCF releases 1.8.1 and 1.9.1, and all systems running an earlier release are at risk.

Risk and Exploitability

The CVSS score of 7.4 indicates a high impact vulnerability. The EPSS score is < 1%, suggesting the likelihood of exploitation is currently low and it is not listed in CISA's KEV catalog. The likely attack vector is over the network; an attacker with network access can intercept a signed SOAP message, capture it, and replay the message without requiring additional privileges. The missing verification step allows the attacker to replay a captured signed envelope.

Generated by OpenCVE AI on July 31, 2026 at 13:46 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade CoreWCF to version 1.8.1 or newer
  • Restart the affected services to load the updated code
  • Monitor service logs for replay activity and enforce stricter authentication if possible

Generated by OpenCVE AI on July 31, 2026 at 13:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-gqv6-pwcg-87r8 CoreWCF: XML Signature Wrapping in WS-Security endorsing/supporting signature verification allows replay of captured signed messages
History

Thu, 09 Jul 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 09 Jul 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Corewcf
Corewcf corewcf
Vendors & Products Corewcf
Corewcf corewcf

Wed, 08 Jul 2026 22:30:00 +0000

Type Values Removed Values Added
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 endorsing and supporting signature verification does not ensure the selected ds:Signature covers the expected Security header target, allowing an attacker with one captured signed SOAP envelope to replay arbitrary service operations as the victim principal. This issue is fixed in versions 1.8.1 and 1.9.1.
Title CoreWCF: XML Signature Wrapping in WS-Security endorsing/supporting signature verification allows replay of captured signed messages
Weaknesses CWE-294
CWE-345
CWE-347
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-10T03:55:39.889Z

Reserved: 2026-06-15T23:23:57.714Z

Link: CVE-2026-54783

cve-icon Vulnrichment

Updated: 2026-07-09T12:55:06.422Z

cve-icon NVD

Status : Deferred

Published: 2026-07-08T23:16:56.173

Modified: 2026-07-10T05:16:37.640

Link: CVE-2026-54783

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-07-31T14:00:07Z

Weaknesses
  • CWE-294

    Authentication Bypass by Capture-replay

  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-347

    Improper Verification of Cryptographic Signature