cve.bz

CVE-2026-54780 corewcf corewcf: Algorithm Downgrade

3.7 lowEPSS 0.2%Fix available

Low (3.7) in corewcf corewcf. EPSS 0.2% 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, 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.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 15th 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-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-327 Use of a Broken or Risky Cryptographic Algorithm
CWE-757 Selection of Less-Secure Algorithm During Negotiation (Algorithm Downgrade)
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-54780 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54780?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54780?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-54780 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-4v55-cpmv-3vcmNuGetCoreWCF.Primitives<1.8.11.8.1
GHSA-4v55-cpmv-3vcmNuGetCoreWCF.Primitives>=1.9.0 <1.9.11.9.1

Attack patterns (CAPEC)

  • CAPEC-220 Client-Server Protocol Manipulation Severity: Medium
  • CAPEC-606 Weakening of Cellular Encryption Severity: High
  • CAPEC-620 Drop Encryption Level Severity: High
  • CAPEC-20 Encryption Brute Forcing Likelihood: Low · Severity: Low
  • CAPEC-97 Cryptanalysis Likelihood: Low · Severity: Very High
  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-473 Signature Spoof
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High
  • CAPEC-608 Cryptanalysis of Cellular Encryption Severity: High
  • CAPEC-614 Rooting SIM Cards Severity: High

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

References

Check your stackJSON