CVE-2025-29774

CRITICALNVD 9.39.3
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 9.1% (95th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this weekElevated
9.3EG
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).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 9.1%CVSS: 9.3Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

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 with a valid account 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.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
73
EG Risk 73/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
The EG Score, 9.3 of 10.
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
9.1%
EPSS %ILE
95th
KEV
Not listed

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.

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

March 14, 2025

Last Modified

April 15, 2026

Advisory Details (8)

Auto-updated Sep 15, 2026
Patch available. Sources: github_release, github, github_commit.
Web page

SAMLStorm: Critical Authentication Bypass in xml-crypto and Node.js libraries — WorkOS

https://workos.com/blog/samlstorm
GitHub advisoryMentions a patch (unverified)

XML Signature Verification Bypass via Multiple SignedInfo References · Advisory · node-saml/xml-crypto · GitHub

https://github.com/node-saml/xml-crypto/security/advisories/GHSA-9p8x-f768-wp2g
GitHub release Patch Available

v6.0.1

Patch available: node-saml/xml-crypto v6.0.1

https://github.com/node-saml/xml-crypto/releases/tag/v6.0.1
GitHub release Patch Available

v3.2.1

Patch available: node-saml/xml-crypto v3.2.1

https://github.com/node-saml/xml-crypto/releases/tag/v3.2.1
GitHub release Patch Available

v2.1.6

Patch available: node-saml/xml-crypto v2.1.6

https://github.com/node-saml/xml-crypto/releases/tag/v2.1.6
GitHub commit Patch Available

commit 8ac6118ee797 (node-saml/xml-crypto)

Patch available: node-saml/xml-crypto v6.0.1 (contains commit 8ac6118ee797)

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

commit 886dc63a8b4b (node-saml/xml-crypto)

Patch available: node-saml/xml-crypto v2.1.6 (contains commit 886dc63a8b4b)

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

commit 28f92218ecbb (node-saml/xml-crypto)

Patch available: node-saml/xml-crypto v3.2.1 (contains commit 28f92218ecbb)

https://github.com/node-saml/xml-crypto/commit/28f92218ecbb8dcbd238afa4efbbd50302aa9aed

Vendor Advisories for CVE-2025-29774(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:1.4.3-17436524612025-04-03redhat
redhatrhdh/rhdh-hub-rhel9:1.52025-03-27redhat

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.1: fixed in 6.0.1
  • 3.0.0 up to 3.2.1: fixed in 3.2.1
  • every version up to 2.1.6: fixed in 2.1.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 36× 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 90 of 194 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-15 17:58 UTCEG score recompute
  2. 2026-10-15 17:58 UTCVendor advisory
  3. 2026-10-15 16:30 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  5. 2026-10-14 11:49 UTCEG score recompute
  6. 2026-10-14 11:49 UTCVendor advisory
  7. 2026-10-13 16:32 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  8. 2026-10-13 11:04 UTCVendor advisory
  9. 2026-10-12 17:13 UTCEG score recompute
  10. 2026-10-12 16:32 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  11. 2026-10-12 11:42 UTCVendor advisory
  12. 2026-10-11 20:45 UTCEG score recompute
  13. 2026-10-11 18:56 UTCEG score recompute
  14. 2026-10-11 15:33 UTCEG score recompute
  15. 2026-10-11 13:47 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  16. 2026-10-10 22:47 UTCOSV refresh
  17. 2026-10-10 19:59 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  18. 2026-10-09 20:06 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  19. 2026-10-08 17:09 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  20. 2026-10-07 23:46 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  21. 2026-10-06 15:16 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  22. 2026-10-05 17:42 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  23. 2026-10-03 14:24 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  24. 2026-10-01 19:49 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  25. 2026-09-30 15:02 UTCEPSS rescoreEPSS 9.1% · 95th percentile
Show 65 more
  1. 2026-09-29 15:19 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  2. 2026-09-28 13:50 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  3. 2026-09-26 15:58 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  4. 2026-09-26 00:24 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  5. 2026-09-24 14:02 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  6. 2026-09-23 13:47 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  7. 2026-09-21 10:49 UTCOSV refresh
  8. 2026-09-20 20:15 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  9. 2026-09-18 19:27 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  10. 2026-09-16 14:07 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  11. 2026-09-16 05:13 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  12. 2026-09-13 16:46 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  13. 2026-09-12 15:00 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  14. 2026-09-11 14:52 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  15. 2026-09-11 09:35 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  16. 2026-09-10 09:33 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  17. 2026-09-08 21:59 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  18. 2026-09-07 16:00 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  19. 2026-09-06 13:46 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  20. 2026-09-04 05:05 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  21. 2026-09-02 14:11 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  22. 2026-09-02 08:44 UTCOSV refresh
  23. 2026-09-01 13:53 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  24. 2026-08-30 19:16 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  25. 2026-08-30 01:21 UTCEPSS rescoreEPSS 9.1% · 95th percentile
  26. 2026-08-28 21:40 UTCEPSS rescoreEPSS 9.2% · 95th percentile
  27. 2026-08-27 14:24 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  28. 2026-08-26 14:45 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  29. 2026-08-25 13:48 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  30. 2026-08-24 14:16 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  31. 2026-08-23 00:18 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  32. 2026-08-21 23:48 UTCEPSS rescoreEPSS 9.2% · 94th percentile
  33. 2026-08-19 17:03 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  34. 2026-08-18 13:47 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  35. 2026-08-16 14:55 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  36. 2026-08-16 07:54 UTCOSV refresh
  37. 2026-08-16 02:13 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  38. 2026-08-15 01:29 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  39. 2026-08-13 21:59 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  40. 2026-08-12 13:50 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  41. 2026-08-10 23:59 UTCEPSS rescoreEPSS 9.1% · 94th percentile
  42. 2026-08-09 13:45 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  43. 2026-08-07 16:26 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  44. 2026-08-06 13:46 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  45. 2026-08-05 19:16 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  46. 2026-08-04 15:09 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  47. 2026-08-03 10:35 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  48. 2026-08-02 02:26 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  49. 2026-08-01 04:15 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  50. 2026-08-01 01:42 UTCOSV refresh
  51. 2026-07-30 16:27 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  52. 2026-07-30 01:29 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  53. 2026-07-28 15:35 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  54. 2026-07-27 14:12 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  55. 2026-07-25 14:17 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  56. 2026-07-24 14:17 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  57. 2026-07-23 02:52 UTCEG score recompute
  58. 2026-07-22 14:07 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  59. 2026-07-21 15:24 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  60. 2026-07-20 17:07 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  61. 2026-07-19 14:30 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  62. 2026-07-19 02:28 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  63. 2026-07-18 10:04 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  64. 2026-07-16 17:02 UTCEPSS rescoreEPSS 9.0% · 94th percentile
  65. 2026-07-15 16:57 UTCEPSS rescoreEPSS 9.0% · 94th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCdemining/Phantom-Signature-Attack
    Published Jan 15, 2026

    Phantom Signature Attack: An Analysis of the Critical Vulnerability CVE-2025-29774 in the Bitcoin Protocol, SIGHASH_SINGLE Implementation Flaws, and the Mathematical Framework for Private Key Recovery in Lost Cryptocurrency Wallets Enabling Unrestricted Control over BTC Assets

    Open source ↗
  • GitHub PoCdemining/Digital-Signature-Forgery-Attack
    Published Jul 23, 2025

    How CVE-2025-29774 Vulnerabilities and the SIGHASH_SINGLE Bug Threaten Multi-Signature Wallet Operational Methods with Fake RawTX

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-29774?
CVE-2025-29774 is a critical-severity vulnerability; its CVE record was published on March 14, 2025. 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…
When was the CVE record for CVE-2025-29774 published?
The CVE record for CVE-2025-29774 was published on March 14, 2025. 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-2025-29774 actively exploited?
CVE-2025-29774 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.1% probability of exploitation in the next 30 days (95th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-29774?
CVE-2025-29774 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2025-29774?
A fix for CVE-2025-29774 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-29774 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-29774

Explore →

Is Your Infrastructure Affected by CVE-2025-29774?

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

Book a Demo →Browse All CVEs