UnmaintainedRUSTSEC-2025-0141 · bincode
RUSTSEC-2025-0141: Bincode is unmaintained
Short answerNot a bug report: bincode is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | bincode |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2025-12-16 |
| Last changed | 2026-01-16 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2025-0141"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i bincode.
Details from the advisory
Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
Alternatives to consider
References
- Package: crates.io/crates/bincode
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0141.html
- Web: git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Same cratebincode: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?