Rust advisories / cve-rs
UnsoundRUSTSEC-2025-0028 · cve-rs
RUSTSEC-2025-0028: cve-rs introduces memory vulnerabilities in safe Rust
Short answercve-rs has an API that can cause undefined behaviour from safe code: cve-rs introduces memory vulnerabilities in safe Rust. No fixed version yet.
| Crate | cve-rs |
|---|---|
| Type | Unsound (memory-corruption) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2025-02-10 |
| Last changed | 2025-05-06 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i cve-rs. - Avoid the affected API, or replace the crate.
Details from the advisory
This crate is a joke and should never be used.
cve-rs provides demonstrations of common memory vulnerabilities (such as buffer overflows and segfaults) implemented completely within safe Rust.
Internally, this crate does not use unsafe code, it instead exploits a soundness bug in rustc: https://github.com/rust-lang/rust/issues/25860
References
- Package: crates.io/crates/cve-rs
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0028.html
- Web: github.com/Speykious/cve-rs
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?