node-saml xml-crypto up to 2.1.5/3.2.0/6.0.0 XML Digital Signature signature verification

Summaryinfo

A vulnerability identified as problematic has been detected in node-saml xml-crypto up to 2.1.5/3.2.0/6.0.0. This affects an unknown part of the component XML Digital Signature Handler. Performing a manipulation results in signature verification. This vulnerability was named CVE-2025-29775. The attack may be initiated remotely. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in node-saml xml-crypto up to 2.1.5/3.2.0/6.0.0. This affects some unknown functionality of the component XML Digital Signature Handler. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

xml-crypto is an XML digital signature and encryption library for Node.js. An attacker may be able to exploit a vulnerability in versions prior to 6.0.1, 3.2.1, and 2.1.6 to bypass authentication or authorization mechanisms in systems that rely on xml-crypto for verifying signed XML documents. The vulnerability allows an attacker to modify a valid signed XML message in a way that still passes signature verification checks. For example, it could be used to alter critical identity or access control attributes, enabling an attacker to escalate privileges or impersonate another user. Users of versions 6.0.0 and prior should upgrade to version 6.0.1 to receive a fix. Those who are still using v2.x or v3.x should upgrade to patched versions 2.1.6 or 3.2.1, respectively.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-29775 since 03/11/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 2.1.6, 3.2.1 or 6.0.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 28f92218ecbb8dcbd238afa4efbbd50302aa9aed is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• node-saml

Name

• xml-crypto

Version

• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5
• 3.0
• 3.1
• 3.2.0
• 6.0

License

• open-source

Website

• Product: https://github.com/node-saml/xml-crypto/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion