Rust advisories / shaman
Unsound LowRUSTSEC-2025-0113 · shaman
RUSTSEC-2025-0113: soundness issue and unmaintained
Short answershaman has an API that can cause undefined behaviour from safe code: soundness issue and unmaintained. No fixed version yet.
| Crate | shaman |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Low (GitHub rating) |
| Published | 2025-05-06 |
| Last changed | 2025-11-04 |
| Also known as | GHSA-7vjm-6qgq-3mrq |
| Affected functions | shaman::cryptoutil::read_u32v_be, shaman::cryptoutil::read_u32v_le, shaman::cryptoutil::read_u64v_be, shaman::cryptoutil::read_u64v_le, shaman::cryptoutil::write_u32v_le, shaman::cryptoutil::write_u64v_le |
What to do
- Find who pulls it in:
cargo tree -i shaman. - Avoid the affected API (
shaman::cryptoutil::read_u32v_be,shaman::cryptoutil::read_u32v_le,shaman::cryptoutil::read_u64v_be,shaman::cryptoutil::read_u64v_le,shaman::cryptoutil::write_u32v_le,shaman::cryptoutil::write_u64v_le), or replace the crate.
Details from the advisory
shaman::cryptoutil::write_u64v_le and other functions mentioned above cannot garantee memory safety of get_unchecked later if both length are zero.
shaman is unmaintained.
References
- Package: crates.io/crates/shaman
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0113.html
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
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?