LibYML: `libyml::string::yaml_string_extend` is unsound and unmaintained
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
In version 0.0.4, `libyml::string::yaml_string_extend` was revised resulting in undefined behaviour, which is unsound. The GitHub project for `libyml` was archived after unsoundness issues were raised. If you rely on this crate, it is highly recommended switching to a maintained alternative. ## Recommended alternatives - [`libyaml-safer`](https://crates.io/crates/libyaml-safer) - [`unsafe-libyaml-norway`](https://crates.io/crates/unsafe-libyaml-norway) - Maintained fork of `unsafe-libyaml`
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | libyml (crates.io) | 0.0.4 – 0.0.5 | — | No fix listed | GHSA-gfxp-f68g-8x78 |
- libyml (crates.io) Vendor— Affected 0.0.4 – 0.0.5 Fixed in — No fix listed GHSA-gfxp-f68g-8x78
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-gfxp-f68g-8x78
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences