# xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing

Advisory record · `GHSA-2xp3-57p7-qf4v`

- **Identifiers:** `GHSA-2xp3-57p7-qf4v` · `CVE-2024-32962`
- **State:** Confirmed
- **Severity:** CVSS 10.0 Critical
- **Critical:** Yes: CVSS 9+
- **Weakness (CWE):** [CWE-347](https://cwe.mitre.org/data/definitions/347.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 1 May 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 1 May 2024, 17:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 10.0: 9.0 or more.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `xml-crypto` (npm): affected `>=4.0.0, <6.0.0`; fixed in `6.0.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 10.0 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0084, the 58th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 1 May 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-2xp3-57p7-qf4v](https://github.com/advisories/GHSA-2xp3-57p7-qf4v)
- [OSV: GHSA-2xp3-57p7-qf4v](https://osv.dev/vulnerability/GHSA-2xp3-57p7-qf4v)
- <https://github.com/node-saml/xml-crypto/security/advisories/GHSA-2xp3-57p7-qf4v>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-32962>
- <https://github.com/node-saml/xml-crypto/pull/301>
- <https://github.com/node-saml/xml-crypto/pull/445>
- <https://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000>
- <https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11ca>
- <https://github.com/node-saml/xml-crypto>
- <https://github.com/node-saml/xml-crypto/discussions/399>
- <https://security.netapp.com/advisory/ntap-20240705-0003>
- <https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidation>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-2xp3-57p7-qf4v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2xp3-57p7-qf4v/>. Everything for agents: <https://agentprime.io/llms.txt>.
