---
title: "CVE-2024-32962: xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing"
url: https://erroneo.us/security/cve/CVE-2024-32962/
description: "CVE-2024-32962 (xml-crypto (npm)): xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration…"
type: vulnerability-record
section: "Security Digest"
date_published: 2024-05-02
date_modified: 2025-02-13
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2024-32962"
kev: false
cvss: 10
epss: 0.00833
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2024-32962: xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.8% , percentile 57: FIRST’s model estimates a 0.8% chance of exploitation activity in the next 30 days, higher than 57% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes xml-crypto (npm) >= 4.0.0, < 6.0.0, fixed in 6.0.0 . Check your lockfile, including transitive dependencies.

## What it is

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-20080610 spec. As such, without additional validation steps, the default configuration allows a malicious actor to re-sign an XML document, place the certificate in a element, and pass xml-crypto default validation checks. As a result xml-crypto trusts by default any certificate provided via digitally signed XML document's . xml-crypto prefers to use any certificate provided via digitally signed XML document's even if library was configured to use specific certificate (publicCert) for signature verification purposes. An attacker can spoof signature verification by modifying XML document and replacing existing signature with signature generated with malicious private key (created by attacker) and by attaching that private key's certificate to element. This vulnerability is combination of changes introduced to 4.0.0 on pull request 301 / commit c2b83f98 and has been addressed in version 6.0.0 with pull request 445 / commit 21201723d. Users are advised to upgrade. Users unable to upgrade may either check the certificate extracted via getCertFromKeyInfo against trusted certificates before accepting the results of the validation or set xml-crypto's getCertFromKeyInfo to () => undefined forcing xml-crypto to use an explicitly configured publicCert or privateKey for signature verification.

## Affected packages

- npm `xml-crypto` >= 4.0.0, < 6.0.0 → fixed: 6.0.0

## Affected products (CVE record)

- node-saml xml-crypto: >= 4.0.0, < 6.0.0

## Severity

- GitHub_M CVSS 3.1: 10 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`
- GitHub CVSS 3.1: 10.0 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.83% probability of exploitation activity in the next 30 days; percentile 57.

## Sources

- [GitHub Advisory GHSA-2xp3-57p7-qf4v](https://github.com/advisories/GHSA-2xp3-57p7-qf4v)
- [CVE.org record CVE-2024-32962](https://www.cve.org/CVERecord?id=CVE-2024-32962)
- [NVD entry CVE-2024-32962](https://nvd.nist.gov/vuln/detail/CVE-2024-32962)
- [github.com](https://github.com/node-saml/xml-crypto/security/advisories/GHSA-2xp3-57p7-qf4v)
- [github.com](https://github.com/node-saml/xml-crypto/pull/301)
- [github.com](https://github.com/node-saml/xml-crypto/pull/445)
- [github.com](https://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000)
- [github.com](https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11ca)
- [w3.org](https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidation)
- [security.netapp.com](https://security.netapp.com/advisory/ntap-20240705-0003/)
- [github.com](https://github.com/node-saml/xml-crypto/discussions/399)

---
Source page: https://erroneo.us/security/cve/CVE-2024-32962/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt