CVE-2024-32962

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2024-05-01. NVD baseline CVSS 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2024-1373 (ENISA EUVD) · GHSA-2xp3-57p7-qf4v (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
57th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 2, 2024

Last Modified

April 15, 2026

Advisory Details (7)

Auto-updated Nov 1, 2026
Patch available. Sources: github_commit, github_pr, github.
GitHub pull request Patch Available

Add support for <X509Certificate /> in <KeyInfo />; remove `KeyInfoProvider`

Patch available: node-saml/xml-crypto v4.0.0 (PR #301 merged 2023-06-17)

https://github.com/node-saml/xml-crypto/pull/301
GitHub commit Patch Available

commit c2b83f984049 (node-saml/xml-crypto)

Patch available: node-saml/xml-crypto v4.0.0 (contains commit c2b83f984049)

https://github.com/node-saml/xml-crypto/commit/c2b83f984049edb68ad1d7c6ad0739ec92af11ca
GitHub commit Patch Available

commit 21201723d2ca (node-saml/xml-crypto)

Patch available: node-saml/xml-crypto v6.0.0 (contains commit 21201723d2ca)

https://github.com/node-saml/xml-crypto/commit/21201723d2ca9bc11288f62cf72552b7d659b000
Web page

XML Signature Syntax and Processing (Second Edition)

https://www.w3.org/TR/2008/REC-xmldsig-core-20080610/#sec-CoreValidation
GitHub advisoryMentions a patch (unverified)

XML signature verification bypass due improper verification of signature / signature spoofing · Advisory · node-saml/xml-crypto · GitHub

https://github.com/node-saml/xml-crypto/security/advisories/GHSA-2xp3-57p7-qf4v
GitHub pull request Patch Available

Set `getCertFromKeyInfo` to `noop`

Patch available: node-saml/xml-crypto v6.0.0 (PR #445 merged 2024-01-26)

https://github.com/node-saml/xml-crypto/pull/445

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmxml-crypto @ 6.0.0 (fixes >= 4.0.0, < 6.0.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
xml-crypto—
  • 4.0.0 up to 6.0.0: fixed in 6.0.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 252 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 156 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  2. 2026-11-02 10:34 UTCEG score recompute
  3. 2026-11-02 10:34 UTCGHSA enrichmentGHSA-2xp3-57p7-qf4v · GitHub severity CRITICAL · GitHub CVSS 10.0
  4. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  5. 2026-11-01 11:26 UTCGHSA enrichmentGHSA-2xp3-57p7-qf4v · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-11-01 08:14 UTCGHSA enrichmentGHSA-2xp3-57p7-qf4v · GitHub severity CRITICAL · GitHub CVSS 10.0
  7. 2026-11-01 08:14 UTCEG score recompute
  8. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  9. 2026-10-31 12:20 UTCEG score recompute
  10. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  11. 2026-10-30 13:12 UTCEG score recompute
  12. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  13. 2026-10-29 14:05 UTCEG score recompute
  14. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  15. 2026-10-28 14:58 UTCEG score recompute
  16. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  17. 2026-10-27 15:37 UTCEG score recompute
  18. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  19. 2026-10-25 17:08 UTCEG score recompute
  20. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  21. 2026-10-24 17:59 UTCEG score recompute
  22. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  23. 2026-10-23 18:53 UTCEG score recompute
  24. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  25. 2026-10-22 19:46 UTCEG score recompute
Show 71 more
  1. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  2. 2026-10-21 20:39 UTCEG score recompute
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  4. 2026-10-20 21:32 UTCEG score recompute
  5. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  6. 2026-10-19 22:25 UTCEG score recompute
  7. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  8. 2026-10-18 21:20 UTCEG score recompute
  9. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  10. 2026-10-18 07:16 UTCEG score recompute
  11. 2026-10-17 22:13 UTCEG score recompute
  12. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  13. 2026-10-16 23:07 UTCEG score recompute
  14. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  15. 2026-10-15 20:14 UTCEG score recompute
  16. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  17. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  18. 2026-10-14 14:10 UTCEG score recompute
  19. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  20. 2026-10-12 17:55 UTCEG score recompute
  21. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  22. 2026-10-11 21:19 UTCEG score recompute
  23. 2026-10-11 16:12 UTCEG score recompute
  24. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  25. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  26. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  27. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  28. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  29. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  30. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  31. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  32. 2026-10-04 10:30 UTCOSV refresh
  33. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  34. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  35. 2026-09-30 19:44 UTCEG score recompute
  36. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  37. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  38. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  39. 2026-09-27 13:43 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  40. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  41. 2026-09-26 00:23 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  42. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  43. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  44. 2026-09-22 14:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  45. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  46. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  47. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  48. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  49. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  50. 2026-09-15 00:14 UTCOSV refresh
  51. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  52. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  53. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  54. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  55. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  56. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  57. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  58. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  59. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  60. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  61. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  62. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  63. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  64. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  65. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  66. 2026-08-26 23:39 UTCOSV refresh
  67. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  68. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  69. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  70. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  71. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile

Frequently asked(5)

What is CVE-2024-32962?
CVE-2024-32962 is a critical-severity vulnerability; its CVE record was published on May 2, 2024. 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…
When was the CVE record for CVE-2024-32962 published?
The CVE record for CVE-2024-32962 was published on May 2, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 15, 2026; the record at its source may have been updated since.
Is CVE-2024-32962 actively exploited?
CVE-2024-32962 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-32962?
CVE-2024-32962 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-32962?
A fix for CVE-2024-32962 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-32962

Explore →

Is Your Infrastructure Affected by CVE-2024-32962?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.