Vulnerabilities in pkg:npm/xml-crypto
PACKAGECVE-2025-29775 is a CRITICAL xml-crypto vulnerable to xml signature vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Xml crypto libraries in the npm ecosystem. The issue involves xml-crypto vulnerable to xml signature verification bypass via digestvalue comment. Remediation is available by upgrading affected packages to version 6.0.1, 3.2.1, 2.1.6.
pkg:npm/xml-crypto
Vulnerability advisories affecting package pkg:npm/xml-crypto. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-x3m8-899r-f7c3 | CVE-2025-29775 | CRITICAL | xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment |
| GHSA-9p8x-f768-wp2g | CVE-2025-29774 | CRITICAL | xml-crypto Vulnerable to XML Signature Verification Bypass via Multiple SignedInfo References |
| GHSA-2xp3-57p7-qf4v | CVE-2024-32962 | CRITICAL | xml-crypto vulnerable to XML signature verification bypass due improper verification of signature/signature spoofing |
| GHSA-c27r-x354-4m68 | - | HIGH | xml-crypto's HMAC-SHA1 signatures can bypass validation via key confusion |
CVE-2025-29775 at a Glance
How to Fix CVE-2025-29775
To remediate this vulnerability, upgrade all affected Xml crypto dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install xml-crypto@6.0.1
npm install xml-crypto@3.2.1
npm install xml-crypto@2.1.6
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls xml-crypto
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2025-29775, inspect your project dependencies using npm:
npm ls xml-crypto
Analyze the terminal output to locate any version of Xml crypto in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.0.1), your application is affected.
Note: The npm ls xml-crypto command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Xml crypto, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2025-29775 Affected Xml crypto Versions
3 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
xml-crypto
|
npm |
≥ 4.0.0
< 6.0.1
|
6.0.1
|
|
xml-crypto
|
npm |
≥ 3.0.0
< 3.2.1
|
3.2.1
|
|
xml-crypto
|
npm |
< 2.1.6
|
2.1.6
|
References
Frequently Asked Questions
What is CVE-2025-29775?
Which Xml crypto versions are affected?
What version fixes CVE-2025-29775?
Is xml-crypto affected?
What CWE is associated with CVE-2025-29775?
How can I check npm dependencies for CVE-2025-29775?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-x3m8-899r-f7c3",
"modified" : "2025-03-16T21:34:52Z",
"published" : "2025-03-14T17:16:47Z",
"aliases" : [ "CVE-2025-29775" ],
"summary" : "xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment",
"details" : "# Impact\nAn attacker may be able to exploit this vulnerability 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.\n\n# Patches\nAll versions <= 6.0.0 are affected. Please upgrade to version 6.0.1.\n\nIf you are still using v2.x or v3.x please upgrade to the associated patch version.\n\n# Indicators of Compromise\n\nWhen logging XML payloads, check for the following indicators. If the payload includes encrypted elements, ensure you analyze the decrypted version for a complete assessment. (If encryption is not used, analyze the original XML document directly). This applies to various XML-based authentication and authorization flows, such as SAML Response payloads.\n\n### Presence of Comments in `DigestValue`\nA `DigestValue` should **not** contain comments. If you find comments within it, this may indicate tampering.\n\n**Example of a compromised `DigestValue`:**\n```xml\n<DigestValue>\n <!--TBlYWE0ZWM4ODI1NjliYzE3NmViN2E1OTlkOGDhhNmI=-->\n c7RuVDYo83z2su5uk0Nla8DXcXvKYKgf7tZklJxL/LZ=\n</DigestValue>\n```\n\n### Code to test\n\nPass in the decrypted version of the document\n```js\ndecryptedDocument = ... // yours to implement\n\nconst digestValues = xpath.select(\n \"//*[local-name()='DigestValue'][count(node()) > 1]\",\n decryptedDocument,\n);\n\nif (digestValues.length > 0) {\n // Compromise detected, yours to implement\n}\n```",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "xml-crypto"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "6.0.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "xml-crypto"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.0.0"
}, {
"fixed" : "3.2.1"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "xml-crypto"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "2.1.6"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/security/advisories/GHSA-x3m8-899r-f7c3"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-29775"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/commit/28f92218ecbb8dcbd238afa4efbbd50302aa9aed"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/commit/886dc63a8b4bb5ae1db9f41c7854b171eb83aa98"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/commit/8ac6118ee7978b46aa56b82cbcaa5fca58c93a07"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/node-saml/xml-crypto"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/releases/tag/v2.1.6"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/releases/tag/v3.2.1"
}, {
"type" : "WEB",
"url" : "https://github.com/node-saml/xml-crypto/releases/tag/v6.0.1"
}, {
"type" : "WEB",
"url" : "https://workos.com/blog/samlstorm"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-347" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2025-03-14T17:16:47Z",
"nvd_published_at" : "2025-03-14T18:15:32Z"
}
}