- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
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
* [wincode](https://crates.io/crates/wincode) * [postcard](https://crates.io/crates/postcard) * [bitcode](https://crates.io/crates/bitcode) * [rkyv](https://crates.io/crates/rkyv)
Is RUSTSEC-2025-0141 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | bincode | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.