cve.bz

CVE-2026-54773 corewcf corewcf

5.9 mediumEPSS 0.4%Fix available

Medium (5.9) in corewcf corewcf. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in CoreWCF.Primitives 1.8.1, 1.9.1.

On this page
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.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • CoreWCF.Primitives (NuGet): fixed in 1.8.1, 1.9.1

Ask an AI about this CVE

Show the promptExplain CVE-2026-54773 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54773?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54773?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54773 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
CoreWCF>= 1.9.0, < 1.9.1
CoreWCF< 1.8.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jc6x-rj79-w4mxNuGetCoreWCF.Primitives<1.8.11.8.1
GHSA-jc6x-rj79-w4mxNuGetCoreWCF.Primitives>=1.9.0 <1.9.11.9.1

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON