- 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
Inserting into an `im::OrdSet` (for example by collecting an iterator into one) can violate Rust's aliasing rules: Miri reports a stacked borrows violation in `sized_chunks::Chunk::force_copy()`, which is called during insertion, where a shared borrow is invalidated by a unique borrow before the read through it completes. This is undefined behavior, reachable from safe code.
No fixed version is available, as the crate is unmaintained; its GitHub repository was archived by the owner on 2026-05-03.
Is RUSTSEC-2023-0126 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 | im | >=0.0.0-0 |
no fix listed |
References
-
crates.io
/crates/im
package
-
rustsec.org
/advisories/RUSTSEC-2023-0126.html
advisory
-
github.com
/bodil/im-rs/issues/207
report
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.