What is GHSA-HHW4-XG65-FP2X?

GHSA-HHW4-XG65-FP2X is a medium-severity out-of-bounds write vulnerability in serde_yml (rust), affecting versions <= 0.0.12. No fixed version is listed yet. A write operation targets a memory location beyond the intended buffer boundary.

Which versions of serde_yml are affected by GHSA-HHW4-XG65-FP2X?

serde_yml (rust) versions <= 0.0.12 is affected.

Is there a fix for GHSA-HHW4-XG65-FP2X?

No fixed version is listed for GHSA-HHW4-XG65-FP2X yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-HHW4-XG65-FP2X exploitable, and should I be worried?

Whether GHSA-HHW4-XG65-FP2X 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-HHW4-XG65-FP2X 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-HHW4-XG65-FP2X in serde_yml

Q: Which versions of serde_yml are affected by GHSA-HHW4-XG65-FP2X?

serde_yml (rust) versions <= 0.0.12 is affected.

Q: Is there a fix for GHSA-HHW4-XG65-FP2X?

No fixed version is listed for GHSA-HHW4-XG65-FP2X yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is GHSA-HHW4-XG65-FP2X exploitable, and should I be worried?

Whether GHSA-HHW4-XG65-FP2X 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-HHW4-XG65-FP2X 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-HHW4-XG65-FP2X?

No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked containers and enable compiler hardening flags.

Summary

serde_yml crate is unsound and unmaintained

Using serde_yml::ser::Serializer.emitter can cause a segmentation fault, which is unsound.

The GitHub project for serde_yml was archived after unsoundness issues were raised.

If you rely on this crate, it is highly recommended switching to a maintained alternative.

Recommended alternatives

serde_norway - Maintained fork of serde_yaml, using unsafe-libyaml-norway
serde_yaml_ng - Maintained fork of serde_yaml, using unmaintained unsafe-libyaml

Incomplete pure Rust alternatives

These implementation do not rely on C libyaml.

Impact

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

Affected versions

serde_yml (<= 0.0.12)

Security releases

Not available

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

No fixed version is listed for GHSA-HHW4-XG65-FP2X yet.

In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked containers and enable compiler hardening flags.

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

Frequently Asked Questions

What is GHSA-HHW4-XG65-FP2X? GHSA-HHW4-XG65-FP2X is a medium-severity out-of-bounds write vulnerability in serde_yml (rust), affecting versions <= 0.0.12. No fixed version is listed yet. A write operation targets a memory location beyond the intended buffer boundary.
Which versions of serde_yml are affected by GHSA-HHW4-XG65-FP2X? serde_yml (rust) versions <= 0.0.12 is affected.
Is there a fix for GHSA-HHW4-XG65-FP2X? No fixed version is listed for GHSA-HHW4-XG65-FP2X yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-HHW4-XG65-FP2X exploitable, and should I be worried? Whether GHSA-HHW4-XG65-FP2X 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-HHW4-XG65-FP2X 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-HHW4-XG65-FP2X? No fixed version is listed yet. In the interim: Keep the dependency up to date. In native-code projects, use bounds-checked containers and enable compiler hardening flags.