CoreWCF up to 1.8.0/1.9.0 WS-Security 1.0 Receive Pipeline weak password hash

Summaryinfo

A vulnerability classified as problematic has been found in CoreWCF up to 1.8.0/1.9.0. This vulnerability affects unknown code of the component WS-Security 1.0 Receive Pipeline. Performing a manipulation results in weak password hash. This vulnerability is identified as CVE-2026-54780. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in CoreWCF up to 1.8.0/1.9.0. It has been classified as problematic. This affects some unknown processing of the component WS-Security 1.0 Receive Pipeline. The manipulation with an unknown input leads to a weak password hash vulnerability. CWE is classifying the issue as CWE-916. The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive. This is going to have an impact on confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-54780 since 06/16/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

Upgrading to version 1.8.1 or 1.9.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• CoreWCF

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.8.0
• 1.9.0

Website

• Product: https://github.com/CoreWCF/CoreWCF/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion