Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-gfxp-f68g-8x78 libyml

GHSA-gfxp-f68g-8x78 is a security vulnerability in libyml. No vendor fix is recorded yet; mitigation options are listed below.

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

Also known asRUSTSEC-2025-0067
Published
Sep 15, 2025
Updated
Oct 28, 2025
Affected
1 pkg
Patched
None yet
Exploits
None indexed
Exploitation data as of Oct 28, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🦀libyml

Real-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

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

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🦀crates.iolibyml0.0.4No fix

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libyml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    No patched version of libyml has shipped for GHSA-gfxp-f68g-8x78 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gfxp-f68g-8x78 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-gfxp-f68g-8x78. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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`
O3 Security · Impact-Aware SCA

Is GHSA-gfxp-f68g-8x78 in your dependencies?

O3 Security finds GHSA-gfxp-f68g-8x78 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-gfxp-f68g-8x78: libyml | O3 Security