RUSTSEC-2026-0105 json
core2 is unmaintained, all versions yanked
published 6mo ago modified 6mo ago
- 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
The maintainer decided stop maintaining crate and yanked all published versions.
Potential alternatives:
- [`embedded-io`](https://crates.io/crates/embedded-io) solves the same general problem - [`no-std-io2`](https://crates.io/crates/no-std-io2) is a maintained fork
Is RUSTSEC-2026-0105 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 | core2 | >=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.