Rust advisories / serde_yml
Unsound MediumRUSTSEC-2025-0068 · serde_yml
RUSTSEC-2025-0068: serde_yml crate is unsound and unmaintained
Short answerserde_yml has an API that can cause undefined behaviour from safe code: serde_yml crate is unsound and unmaintained. No fixed version yet.
| Crate | serde_yml |
|---|---|
| Type | Unsound |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Medium (GitHub rating) |
| Published | 2025-09-11 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-hhw4-xg65-fp2x |
What to do
- Find who pulls it in:
cargo tree -i serde_yml. - Avoid the affected API, or replace the crate.
Details from the advisory
Using serde_yml::ser::Serializer.emitter can cause a segmentation fault, which is unsound.
The GitHub project for serde_yml was archived after unsoundness issues were raised.
If you rely on this crate, it is highly recommended switching to a maintained alternative.
Recommended alternatives
serde_norway- Maintained fork ofserde_yaml, usingunsafe-libyaml-norwayserde_yaml_ng- Maintained fork ofserde_yaml, using unmaintainedunsafe-libyaml
Incomplete pure Rust alternatives
These implementation do not rely on C libyaml.
References
- Package: crates.io/crates/serde_yml
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0068.html
- Report: github.com/rustsec/advisory-db/issues/2395
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?