Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

xml-crypto Vulnerable to XML Signature Verification Bypass via DigestValue Comment

CVSS 4.0 9.3 CRITICALEUVD CVSS 4.0 9.3 CVSS 4.0 · [email protected] · Secondary 9.3 CRITICALCVSS_V4 Publisher rating CRITICALFixed by xml-crypto 6.0.1Fixed by xml-crypto 3.2.1Fixed by xml-crypto 2.1.6KEV status unknown

cve-program · CVE-2025-29775

Published

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.

Read the publisher's advisory

euvd · EUVD-2025-7891

Published

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.

Read the publisher's advisory

nvd · CVE-2025-29775

Published

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.

Read the publisher's advisory

osv · GHSA-x3m8-899r-f7c3

Published

# Impact An 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. # Patches All versions <= 6.0.0 are affected. Please upgrade to version 6.0.1. If you are still using v2.x or v3.x please upgrade to the associated patch version. # Indicators of Compromise When 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. ### Presence of Comments in `DigestValue` A `DigestValue` should **not** contain comments. If you find comments within it, this may indicate tampering. **Example of a compromised `DigestValue`:** ```xml <DigestValue> <!--TBlYWE0ZWM4ODI1NjliYzE3NmViN2E1OTlkOGDhhNmI=--> c7RuVDYo83z2su5uk0Nla8DXcXvKYKgf7tZklJxL/LZ= </DigestValue> ``` ### Code to test Pass in the decrypted version of the document ```js decryptedDocument = ... // yours to implement const digestValues = xpath.select( "//*[local-name()='DigestValue'][count(node()) > 1]", decryptedDocument, ); if (digestValues.length > 0) { // Compromise detected, yours to implement } ```

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-29775

Published

xml-crypto

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "node-saml",
                    "product": "xml-crypto",
                    "versions": [
                        {
                            "version": ">= 4.0.0, < 6.0.1",
                            "status": "affected"
                        },
                        {
                            "version": ">= 3.0.0, < 3.2.1",
                            "status": "affected"
                        },
                        {
                            "version": "< 2.1.6",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-7891

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Mar 14, 2025, 5:11:05 PM

dateUpdated: Mar 15, 2025, 8:45:45 PM

5 related source bulletins · separate from aliases

RHSA-2025:3374: Red Hat Security Advisory: Red Hat Developer Hub 1.5.1 release.

CVE-2024-45338 · CVE-2024-47068 · CVE-2024-52798 · CVE-2024-55565 · CVE-2024-56201 · CVE-2024-56326 · CVE-2024-56334 · CVE-2025-22150 · CVE-2025-27516 · CVE-2025-29774 · CVE-2025-29775

RHSA-2025:7626: Red Hat Security Advisory: Red Hat Developer Hub 1.6.0 release.

CVE-2024-12905 · CVE-2024-21534 · CVE-2025-26791 · CVE-2025-29775

WID-SEC-W-2025-0841: IBM App Connect Enterprise: Mehrere Schwachstellen

CVE-2024-57965 · CVE-2025-27152 · CVE-2025-29774 · CVE-2025-29775

RHSA-2025:3595: Red Hat Security Advisory: Red Hat Developer Hub 1.4.3 release.

CVE-2025-27516 · CVE-2025-29774 · CVE-2025-29775

WID-SEC-W-2025-0705: HCL BigFix WebUI-Anwendungen: Mehrere Schwachstellen

CVE-2024-47764 · CVE-2025-25977 · CVE-2025-27152 · CVE-2025-27789 · CVE-2025-29774 · CVE-2025-29775

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-29775

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-347

Original publisher date fields

published: 2025-03-14T18:15:32.180

lastModified: 2026-06-17T09:05:39.033

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-x3m8-899r-f7c3

Published

xml-crypto

npm

SEMVER · introduced 4.0.0 → fixed 6.0.1

xml-crypto

npm

SEMVER · introduced 3.0.0 → fixed 3.2.1

xml-crypto

npm

SEMVER · introduced 0 → fixed 2.1.6

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current