● 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
| If you run | Upgrade to | Advisories |
|---|---|---|
| From 0.9.0-beta.1 before 0.9.0-beta.7.0 | 0.9.0-beta.7.0 | 5 advisories |
| Before 0.8.9 | 0.8.9 | 5 advisories |
Security advisories, newest first
| Advisory | What it is | Affects | Fixed in | Published |
|---|---|---|---|---|
| RUSTSEC-2026-0529 | KVStoreInterpreter::verify_signature_legacy answers true for every token and every key | From 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.9 | 0.8.9, 0.9.0-beta.7.0 | |
| RUSTSEC-2026-0501 | Shamir backup recovery accepts a share at x = 0, so a supplied share can substitute the recovered private key | From 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.7 | 0.8.7, 0.9.0-beta.7.0 | |
| RUSTSEC-2026-0497 | Transaction::from_json holds an input txid that is not 64 hex digits and writes the input as spending the zero txid | From 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.6 | 0.8.6, 0.9.0-beta.7.0 | |
| RUSTSEC-2026-0499 | Signature::from_der reads a signature with bytes after it, a wrong sequence length or an unneeded zero as the signature | From 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.6 | 0.8.6, 0.9.0-beta.7.0 | |
| RUSTSEC-2026-0498RUSTSEC-2026-0500 | Transaction readers accept trailing bytes, so a parsed transaction can carry another transaction id | From 0.9.0-beta.1 before 0.9.0-beta.7.0; Before 0.8.5 | 0.8.5, 0.9.0-beta.7.0 |
Other crates.io crates
- aws-lc-sys5 advisories
- bottlerocket/update-operator5 advisories
- comrak5 advisories
- cosmwasm-vm5 advisories