How severe is GHSA-gfxp-f68g-8x78?

No CVSS score has been assigned to GHSA-gfxp-f68g-8x78 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gfxp-f68g-8x78?

GHSA-gfxp-f68g-8x78 affects the following packages: libyml (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-gfxp-f68g-8x78?

The records we use list no patched version of libyml for GHSA-gfxp-f68g-8x78. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect GHSA-gfxp-f68g-8x78 in my crates.io dependencies?

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.

How do I mitigate GHSA-gfxp-f68g-8x78 if there is no patch (or I can't update yet)?

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.

Is GHSA-gfxp-f68g-8x78 actively exploited in the wild?

No public exploit code has been indexed for GHSA-gfxp-f68g-8x78 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-gfxp-f68g-8x78 published, and has it been updated?

GHSA-gfxp-f68g-8x78 was published on September 15, 2025 and was last updated on October 28, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

LibYML: `libyml::string::yaml_string_extend` is unsound and unmaintainedGHSA-gfxp-f68g-8x78

GHSA-gfxp-f68g-8x78 is a security vulnerability in libyml. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

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

libyaml-safer
unsafe-libyaml-norway - Maintained fork of unsafe-libyaml

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libyml`	≥ 0.0.4	No fix

Detection & mitigation playbook

Open-source dependency

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.
Remediation status
The records we use list no patched version of libyml for GHSA-gfxp-f68g-8x78. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
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.

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?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works