cve.bz

CVE-2025-29775 (SAMLStorm) node-saml xml-crypto

9.3 criticalEPSS 10%Fix available

Known as SAMLStorm

Critical (9.3) in node-saml xml-crypto. EPSS 10% estimated probability of exploitation activity in the next 30 days. Fixed in xml-crypto 2.1.6, 3.2.1, 6.0.1.

On this page
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 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.

Severity

CVSS 4.0

9.3 critical
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
EPSS
10% (unchanged from 10% a week ago; 9.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: total, assessed 2025-03-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • xml-crypto (npm): fixed in 6.0.1, 3.2.1, 2.1.6

Ask an AI about this CVE

Show the promptExplain CVE-2025-29775 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-29775?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-29775?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-29775 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
node-saml xml-crypto>= 4.0.0, < 6.0.1
node-saml xml-crypto>= 3.0.0, < 3.2.1
node-saml xml-crypto< 2.1.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x3m8-899r-f7c3npmxml-crypto>=4.0.0 <6.0.16.0.1
GHSA-x3m8-899r-f7c3npmxml-crypto>=3.0.0 <3.2.13.2.1
GHSA-x3m8-899r-f7c3npmxml-crypto<2.1.62.1.6

Red Hat

Red Hat rates this Important.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Red Hat Developer Hub 1.5rhdh/rhdh-hub-rhel9:1.5Fixed 2025-03-27RHSA-2025:3374
Red Hat Developer Hub 1.6rhdh/rhdh-hub-rhel9:1.6.0-1745956724Fixed 2025-05-14RHSA-2025:7626
Red Hat Developer Hub (RHDH) 1.4rhdh/rhdh-hub-rhel9:1.4.3-1743652461Fixed 2025-04-03RHSA-2025:3595
OpenShift Serverlessopenshift-serverless-1/kn-backstage-plugins-eventmesh-rhel8Will not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-29775.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

  • Emerging Threats Open ET WEB_SPECIFIC_APPS xml-crypto / Node.js SAML Authentication Bypass Forged DigestValue Comment (CVE-2025-29775) sid 2060960

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON