What is GHSA-R24F-HG58-VFRW?

GHSA-R24F-HG58-VFRW is a medium-severity security vulnerability in unsafe-libyaml (rust), affecting versions < 0.2.10. It is fixed in 0.2.10.

Which versions of unsafe-libyaml are affected by GHSA-R24F-HG58-VFRW?

unsafe-libyaml (rust) versions < 0.2.10 is affected.

Is there a fix for GHSA-R24F-HG58-VFRW?

Yes. GHSA-R24F-HG58-VFRW is fixed in 0.2.10. Upgrade to this version or later.

Is GHSA-R24F-HG58-VFRW exploitable, and should I be worried?

Whether GHSA-R24F-HG58-VFRW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-R24F-HG58-VFRW is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-R24F-HG58-VFRW in unsafe-libyaml

Q: Which versions of unsafe-libyaml are affected by GHSA-R24F-HG58-VFRW?

unsafe-libyaml (rust) versions < 0.2.10 is affected.

Q: Is there a fix for GHSA-R24F-HG58-VFRW?

Yes. GHSA-R24F-HG58-VFRW is fixed in 0.2.10. Upgrade to this version or later.

Q: Is GHSA-R24F-HG58-VFRW exploitable, and should I be worried?

Whether GHSA-R24F-HG58-VFRW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-R24F-HG58-VFRW is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-R24F-HG58-VFRW?

Upgrade unsafe-libyaml to 0.2.10 or later.

Summary

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

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.

Impact

Affected versions

unsafe-libyaml (< 0.2.10)

Security releases

unsafe-libyaml → 0.2.10 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade unsafe-libyaml to 0.2.10 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-R24F-HG58-VFRW? GHSA-R24F-HG58-VFRW is a medium-severity security vulnerability in unsafe-libyaml (rust), affecting versions < 0.2.10. It is fixed in 0.2.10.
Which versions of unsafe-libyaml are affected by GHSA-R24F-HG58-VFRW? unsafe-libyaml (rust) versions < 0.2.10 is affected.
Is there a fix for GHSA-R24F-HG58-VFRW? Yes. GHSA-R24F-HG58-VFRW is fixed in 0.2.10. Upgrade to this version or later.
Is GHSA-R24F-HG58-VFRW exploitable, and should I be worried? Whether GHSA-R24F-HG58-VFRW is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-R24F-HG58-VFRW is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-R24F-HG58-VFRW? Upgrade unsafe-libyaml to 0.2.10 or later.