Skip to content
OpenAdvisories

Product · node-saml

xml-crypto

3 known vulnerabilities.

xml-crypto at a glance

Last 12 months
0
Critical · all time
3
Exploited · all time
0
Public exploit · all time
3
New vulnerabilities per month · last 12 months
0 1 1 December 2025: 0 vulnerabilities Dec 2025 January 2026: 0 vulnerabilities February 2026: 0 vulnerabilities March 2026: 0 vulnerabilities Mar April 2026: 0 vulnerabilities May 2026: 0 vulnerabilities June 2026: 0 vulnerabilities Jun July 2026: 0 vulnerabilities August 2026: 0 vulnerabilities September 2026: 0 vulnerabilities Sep October 2026: 0 vulnerabilities November 2026: 0 vulnerabilities
Show as table
MonthVulnerabilitiesCritical
Nov 202600
Oct 202600
Sep 202600
Aug 202600
Jul 202600
Jun 202600
May 202600
Apr 202600
Mar 202600
Feb 202600
Jan 202600
Dec 202500
Nov 202500
Oct 202500
Sep 202500
Aug 202500
Jul 202500
Jun 202500
May 202500
Apr 202500
Mar 202522
Feb 202500
Jan 202500
Dec 202400

3 results · Feed

  • Critical 9.3
    CVE-2025-29775 Public exploit EPSS 10%

    xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment

    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 …

  • Critical 9.3
    CVE-2025-29774 Public exploit

    xml-crypto Vulnerable to XML Signature Verification Bypass via Multiple SignedInfo References

    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 …

  • Critical 10.0
    CVE-2024-32962 Public exploit

    XML signature verification bypass due improper verification of signature / signature spoofing

    xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration does not check authorization of the signer, it only checks the validity of the signature per section 3.2.2 of the w3 xmldsig-core-2008061…