How severe is GHSA-r24f-hg58-vfrw?

No CVSS score has been assigned to GHSA-r24f-hg58-vfrw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-r24f-hg58-vfrw?

GHSA-r24f-hg58-vfrw affects the following packages: unsafe-libyaml (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-r24f-hg58-vfrw?

Update unsafe-libyaml to 0.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r24f-hg58-vfrw is resolved across your whole dependency graph.

How do I detect GHSA-r24f-hg58-vfrw in my crates.io dependencies?

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

How do I mitigate GHSA-r24f-hg58-vfrw 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.

How does O3 Security protect against GHSA-r24f-hg58-vfrw?

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

Is GHSA-r24f-hg58-vfrw actively exploited in the wild?

No public exploit code has been indexed for GHSA-r24f-hg58-vfrw 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-r24f-hg58-vfrw published, and has it been updated?

GHSA-r24f-hg58-vfrw was published on December 21, 2023 and was last updated on September 10, 2026. 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

GHSA-r24f-hg58-vfrw — unsafe-libyaml

Fix: dtolnay/unsafe-libyaml@7755559

GHSA-r24f-hg58-vfrw is a security vulnerability in unsafe-libyaml. A fix is available for unsafe-libyaml — see the affected versions and patch details below.

unsafe-libyaml unaligned write of u64 on 32-bit and 16-bit platforms

Also known asRUSTSEC-2023-0075

Published

Dec 21, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀unsafe-libyaml

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

Affected versions allocate memory using the alignment of usize and write data to it of type u64, without using core::ptr::write_unaligned. In platforms with sub-64bit alignment for usize (including wasm32 and x86) these writes are insufficiently aligned some of the time.

If using an ordinary optimized standard library, the bug exhibits Undefined Behavior so may or may not behave in any sensible way, depending on optimization settings and hardware and other things. If using a Rust standard library built with debug assertions enabled, the bug manifests deterministically in a crash (non-unwinding panic) saying "ptr::write requires that the pointer argument is aligned and non-null".

No 64-bit platform is impacted by the bug.

The flaw was corrected by allocating with adequately high alignment on all platforms.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`unsafe-libyaml`	all versions	0.2.10`cargo update -p unsafe-libyaml --precise 0.2.10`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for unsafe-libyaml, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update unsafe-libyaml to 0.2.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r24f-hg58-vfrw is resolved across your whole dependency graph.
Workarounds
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r24f-hg58-vfrw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r24f-hg58-vfrw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Affected versions allocate memory using the alignment of `usize` and write data to it of type `u64`, without using `core::ptr::write_unaligned`. In platforms with sub-64bit alignment for `usize` (including wasm32 and x86) these writes are insufficiently aligned some of the time. If using an ordinary optimized standard library, the bug exhibits Undefined Behavior so may or may not behave in any sensible way, depending on optimization settings and hardware and other things. If using a Rust standard library built with debug assertions enabled, the bug manifests deterministically in a crash (non-

O3 Security · Impact-Aware SCA

Is GHSA-r24f-hg58-vfrw in your dependencies?

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

Scan my dependencies How O3 SCA works