Rust advisories / mp3-metadata
Unsound MediumRUSTSEC-2025-0027 · mp3-metadata
RUSTSEC-2025-0027: Panic in mp3-metadata due to the lack of bounds checking
Short answermp3-metadata has an API that can cause undefined behaviour from safe code: Panic in mp3-metadata due to the lack of bounds checking. Fixed in 0.4.0.
| Crate | mp3-metadata |
|---|---|
| Type | Unsound (denial-of-service) |
| Affected versions | Before 0.4.0. |
| Fixed in | 0.4.0 |
| Severity | Medium (GitHub rating) |
| Published | 2025-04-28 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-927q-g9w9-pm54 |
| Affected functions | mp3_metadata::read_from_slice |
What to do
- See which version you have:
cargo tree -i mp3-metadata(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p mp3-metadata. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplemp3-metadata = "0.4.0") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
The get_id3() methods used by mp3_metadata::read_from_slice() does not perform adequate bounds checking when recreating the tag due to the use of desynchronization.
Fixed in Fix index error, released as part of 0.4.0.
References
- Package: crates.io/crates/mp3-metadata
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0027.html
- Report: github.com/GuillaumeGomez/mp3-metadata/issues/36
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?