Rust advisories / crate
Security history · zebra-state · data from Oct 24, 2026
Is zebra-state safe to use? Its security history
VerdictNo open advisories. 4 past vulnerabilities were fixed.
4advisories on record
4vulnerabilities
0unmaintained notices
nonenewest fixed version
Every advisory, newest first
- VulnerabilityGHSA-2gf8-q9rr-jq3h · 2026-07-02zebrad has persistent on-disk corruption of Sapling/Orchard subtree roots after chain fork via pop_tip
- VulnerabilityGHSA-hhm7-qrv5-h4r6 · 2026-07-02Zebra: Repeated Non-Finalized Shielded Transaction Aborts Zebra Before Duplicate-Nullifier Rejection
- VulnerabilityGHSA-w834-cf6p-9m9w · 2026-07-02Zebra: Finalized address balance credit-first overflow on consensus-valid blocks
- VulnerabilityGHSA-4m69-67m6-prqp · 2026-07-02Zebra has block suppression via NU5 same-header body poisoning of sent-hash cache
Check your version
Run cargo tree -i zebra-state to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?