xml-crypto (npm) has 4 known vulnerabilities, the worst rated CRITICAL. Upgrade to 6.0.1 or later to clear all of them. No malicious-package signal is recorded.
An attacker may be able to exploit this vulnerability to bypass authentication or authorization mechanisms in systems that rely on xml-crypto for verifying…
CyberXYZ does not call a package safe in absolute terms. It records 4 known vulnerabilities for xml-crypto (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does xml-crypto have known vulnerabilities?
Yes. CyberXYZ records 4 known vulnerabilities for xml-crypto (npm), the worst rated CRITICAL. They are GHSA-x3m8-899r-f7c3, GHSA-9p8x-f768-wp2g, GHSA-2xp3-57p7-qf4v, GHSA-c27r-x354-4m68.
Which version of xml-crypto should I use?
6.0.1 or later clears every advisory recorded for xml-crypto (npm). Check the release you pick before installing it.
How do I check xml-crypto before installing?
Search xml-crypto in CyberXYZ Check at https://cyberxyz.io/check?q=xml-crypto. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 06:52 UTC. The most recent advisory here was published 2025-03-14. Updated continuously from NVD, GHSA, OSV and CNA feeds.