Skip to content
Fencer Intel
high —

GHSA-gfxp-f68g-8x78 json

LibYML: `libyml::string::yaml_string_extend` is unsound and unmaintained

published last yr. modified last yr. also RUSTSEC-2025-0067

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

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`

Is GHSA-gfxp-f68g-8x78 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io libyml
>=0.0.4, <=0.0.5
>=0.0.0-0
 no fix listed

Classification

Weakness
  • CWE-758 Reliance on Undefined, Unspecified, or Implementation-Defined Behavior

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.