VulnerableCode Package Details - pkg:npm/xml-crypto@6.0.0

Search for packages

Vulnerability	Summary	Fixed by
VCID-4tqa-t2nc-w3b3 Aliases: CVE-2025-29774 GHSA-9p8x-f768-wp2g	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.	6.0.1 Affected by 0 other vulnerabilities.
VCID-aran-uatn-kygp Aliases: CVE-2025-29775 GHSA-x3m8-899r-f7c3	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.	6.0.1 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-4tqa-t2nc-w3b3
Aliases:
CVE-2025-29774
GHSA-9p8x-f768-wp2g

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.

6.0.1
Affected by 0 other vulnerabilities.

VCID-aran-uatn-kygp
Aliases:
CVE-2025-29775
GHSA-x3m8-899r-f7c3

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.

6.0.1
Affected by 0 other vulnerabilities.

Vulnerability	Summary	Aliases
VCID-ccf5-gzyd-d7b5	xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration does not check authorization of the signer, it only checks the validity of the signature per section 3.2.2 of the w3 xmldsig-core-20080610 spec. As such, without additional validation steps, the default configuration allows a malicious actor to re-sign an XML document, place the certificate in a `<KeyInfo />` element, and pass `xml-crypto` default validation checks. As a result `xml-crypto` trusts by default any certificate provided via digitally signed XML document's `<KeyInfo />`. `xml-crypto` prefers to use any certificate provided via digitally signed XML document's `<KeyInfo />` even if library was configured to use specific certificate (`publicCert`) for signature verification purposes. An attacker can spoof signature verification by modifying XML document and replacing existing signature with signature generated with malicious private key (created by attacker) and by attaching that private key's certificate to `<KeyInfo />` element. This vulnerability is combination of changes introduced to `4.0.0` on pull request 301 / commit `c2b83f98` and has been addressed in version 6.0.0 with pull request 445 / commit `21201723d`. Users are advised to upgrade. Users unable to upgrade may either check the certificate extracted via `getCertFromKeyInfo` against trusted certificates before accepting the results of the validation or set `xml-crypto's getCertFromKeyInfo` to `() => undefined` forcing `xml-crypto` to use an explicitly configured `publicCert` or `privateKey` for signature verification.	CVE-2024-32962 GHSA-2xp3-57p7-qf4v

Vulnerability

Summary

Aliases

VCID-ccf5-gzyd-d7b5

xml-crypto is an xml digital signature and encryption library for Node.js. In affected versions the default configuration does not check authorization of the signer, it only checks the validity of the signature per section 3.2.2 of the w3 xmldsig-core-20080610 spec. As such, without additional validation steps, the default configuration allows a malicious actor to re-sign an XML document, place the certificate in a `<KeyInfo />` element, and pass `xml-crypto` default validation checks. As a result `xml-crypto` trusts by default any certificate provided via digitally signed XML document's `<KeyInfo />`. `xml-crypto` prefers to use any certificate provided via digitally signed XML document's `<KeyInfo />` even if library was configured to use specific certificate (`publicCert`) for signature verification purposes. An attacker can spoof signature verification by modifying XML document and replacing existing signature with signature generated with malicious private key (created by attacker) and by attaching that private key's certificate to `<KeyInfo />` element. This vulnerability is combination of changes introduced to `4.0.0` on pull request 301 / commit `c2b83f98` and has been addressed in version 6.0.0 with pull request 445 / commit `21201723d`. Users are advised to upgrade. Users unable to upgrade may either check the certificate extracted via `getCertFromKeyInfo` against trusted certificates before accepting the results of the validation or set `xml-crypto's getCertFromKeyInfo` to `() => undefined` forcing `xml-crypto` to use an explicitly configured `publicCert` or `privateKey` for signature verification.

CVE-2024-32962
GHSA-2xp3-57p7-qf4v

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-06-12T19:54:57.637988+00:00	GitLab Importer	Affected by	VCID-4tqa-t2nc-w3b3	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/npm/xml-crypto/CVE-2025-29774.yml	38.6.0
2026-06-12T19:54:55.832829+00:00	GitLab Importer	Affected by	VCID-aran-uatn-kygp	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/npm/xml-crypto/CVE-2025-29775.yml	38.6.0
2026-06-12T19:26:46.783866+00:00	GitLab Importer	Fixing	VCID-ccf5-gzyd-d7b5	https://gitlab.com/gitlab-org/advisories-community/-/blob/main/npm/xml-crypto/CVE-2024-32962.yml	38.6.0
2026-06-12T07:44:44.208943+00:00	GithubOSV Importer	Fixing	VCID-ccf5-gzyd-d7b5	https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/05/GHSA-2xp3-57p7-qf4v/GHSA-2xp3-57p7-qf4v.json	38.6.0
2026-06-11T20:34:36.666010+00:00	GHSA Importer	Fixing	VCID-ccf5-gzyd-d7b5	https://github.com/advisories/GHSA-2xp3-57p7-qf4v	38.6.0