Skip to content
Fencer Vulns
critical 9.3

CVE-2025-29774 json

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

published 2025-03-14 19 mo ago modified 2026-09-10 1 mo ago also GHSA-9p8x-f768-wp2g , EUVD-2025-7890

cvss
9.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
9.1%
EPSS 9.1% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm xml-crypto 2.1.6, 3.2.1, 6.0.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-29774 updated cvss 9.1

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

  • Red Hat OpenShift Serverless openshift-serverless-1/kn-backstage-plugins-eventmesh-rhel8
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Developer Hub (RHDH) 1.4 rhdh 1.4.3-1743652461
    fixed: vendor fix RHSA-2025:3595
  • Red Hat Developer Hub 1.5 rhdh
    fixed: vendor fix RHSA-2025:3374
  • Red Hat Developer Hub (RHDH) 1.4 rhdh 1.4.3-1743648196, rhdh 1.4.3-1743659048 Red Hat Developer Hub 1.5 rhdh
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
19 mo ago

Exploit prediction

9.10% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 4.0 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
npm xml-crypto
>=4.0.0, <6.0.1
>=3.0.0, <3.2.1
<2.1.6
6.0.1
3.2.1
2.1.6

Affected products

  • node-saml xml-crypto

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.