Vulnerability Database · crates.io · zeroize · Version
zeroize 0.5.1
No vulnerabilities in this database cover 0.5.1.
Every vulnerability Vulert holds for zeroize was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.
Critical 0 High 0 Medium 0 Low 0 Unrated 0
-
Released 24 Dec 2018
Status deprecated release
Licence Apache-2.0 OR MIT
Also known from other sources 0
Newer releases 47
Database updated 23/Oct/2026
Release and licence data published by crates.io. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
zeroize 0.5.1 vulnerabilities
No vulnerability in the Vulert database covers zeroize 0.5.1. See the versions that are affected →
Looking for another version, or everything Vulert holds for zeroize?
Questions
About zeroize 0.5.1
Is zeroize 0.5.1 vulnerable?
No. No vulnerability in the Vulert database covers zeroize 0.5.1. Every vulnerability Vulert holds for zeroize was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.
Is 0.5.1 the latest release of zeroize?
No. 0.5.1 was published 24 Dec 2018, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor zeroize for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the zeroize version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.