CISA list

● crates.io crate

bsv-rs

Bsv-rs has five security advisories. The newest release any of them names as the fix is 0.9.0-beta.7.0, a pre-release.

As of , bsv-rs has five security advisories. The newest release any of them names as the fix is 0.9.0-beta.7.0, a pre-release.

Your version, and the version to upgrade to

Find the row your installed version falls in. The second column is the first release after it that none of the advisories lists as affected; a release outside every row is one no advisory lists. That is what the advisories say, not a promise that a release is free of flaws.
If you runUpgrade toAdvisories
From 0.9.0-beta.1 before 0.9.0-beta.7.00.9.0-beta.7.05 advisories
Before 0.8.90.8.95 advisories

Security advisories, newest first

Security advisories, newest first
AdvisoryWhat it isAffectsFixed inPublished
RUSTSEC-2026-0529KVStoreInterpreter::verify_signature_legacy answers true for every token and every keyFrom 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.90.8.9, 0.9.0-beta.7.0
RUSTSEC-2026-0501Shamir backup recovery accepts a share at x = 0, so a supplied share can substitute the recovered private keyFrom 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.70.8.7, 0.9.0-beta.7.0
RUSTSEC-2026-0497Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero txidFrom 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.60.8.6, 0.9.0-beta.7.0
RUSTSEC-2026-0499Signature::from_der reads a signature with bytes after it, a wrong sequence length or an unneeded zero as the signatureFrom 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.60.8.6, 0.9.0-beta.7.0
RUSTSEC-2026-0498RUSTSEC-2026-0500Transaction readers accept trailing bytes, so a parsed transaction can carry another transaction idFrom 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.50.8.5, 0.9.0-beta.7.0

Other crates.io crates