class-validator (npm) has 1 known vulnerability, the worst rated CRITICAL. Upgrade to 0.14.0 or later to clear it. No malicious-package signal is recorded.
In TypeStack class-validator, validate() input validation can be bypassed because certain internal attributes can be overwritten via a conflicting name.
CyberXYZ does not call a package safe in absolute terms. It records 1 known vulnerability for class-validator (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does class-validator have known vulnerabilities?
Yes. CyberXYZ records 1 known vulnerability for class-validator (npm), the worst rated CRITICAL. They are GHSA-fj58-h2fr-3pp2.
Which version of class-validator should I use?
0.14.0 or later clears every advisory recorded for class-validator (npm). Check the release you pick before installing it.
How do I check class-validator before installing?
Search class-validator in CyberXYZ Check at https://cyberxyz.io/check?q=class-validator. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 09:16 UTC. The most recent advisory here was published 2021-10-12. Updated continuously from NVD, GHSA, OSV and CNA feeds.