Rust advisories / unsafe-libyaml
UnmaintainedRUSTSEC-2024-0449 · unsafe-libyaml
RUSTSEC-2024-0449: unsafe-libyaml is unmaintained
Short answerNot a bug report: unsafe-libyaml is no longer maintained, so future security issues will not be fixed. Plan to move to a maintained alternative.
| Crate | unsafe-libyaml |
|---|---|
| Type | Unmaintained |
| Affected versions | Every version. |
| Fixed in | not applicable (the crate is unmaintained) |
| Severity | not scored |
| Published | 2024-03-25 |
| Last changed | 2026-10-12 |
| Also known as | none |
What to do
- Look for a maintained fork or alternative crate.
- If you cannot move yet, acknowledge it in your audit config so CI stays green while you plan: add
"RUSTSEC-2024-0449"toignorein.cargo/audit.tomlordeny.toml, with a comment saying why. - Find who pulls it in:
cargo tree -i unsafe-libyaml.
Details from the advisory
The repository was archived by its owner on 2024-03-25 and is read-only. The last release is 0.2.11 (March 2024).
unsafe-libyaml is a machine translation of libyaml's C code into unsafe Rust (c2rust). Bugs found in it will not be fixed upstream. It is used by serde_yaml (itself deprecated) and by forks such as serde_yaml_ng.
Alternatives
Consider a YAML parser written in safe Rust, for example:
- saphyr (serde-saphyr for serde users)
- noyalib
References
- Package: crates.io/crates/unsafe-libyaml
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0449.html
- Web: github.com/dtolnay/unsafe-libyaml
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for unsafe-libyaml
Up next
Same crateunsafe-libyaml: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?