GHSA-hhw4-xg65-fp2x
serde_yml crate is unsound and unmaintained
Blast Radius
serde_ymlReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | serde_yml | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for serde_yml. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of serde_yml has shipped for GHSA-hhw4-xg65-fp2x yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-hhw4-xg65-fp2x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-hhw4-xg65-fp2x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-hhw4-xg65-fp2x in your dependencies?
O3 detects GHSA-hhw4-xg65-fp2x across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.