How severe is GHSA-hhw4-xg65-fp2x?

No CVSS score has been assigned to GHSA-hhw4-xg65-fp2x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hhw4-xg65-fp2x?

GHSA-hhw4-xg65-fp2x affects the following packages: serde_yml (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-hhw4-xg65-fp2x?

The records we use list no patched version of serde_yml for GHSA-hhw4-xg65-fp2x. 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-hhw4-xg65-fp2x in my crates.io dependencies?

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

How do I mitigate GHSA-hhw4-xg65-fp2x 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-hhw4-xg65-fp2x actively exploited in the wild?

No public exploit code has been indexed for GHSA-hhw4-xg65-fp2x 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-hhw4-xg65-fp2x published, and has it been updated?

GHSA-hhw4-xg65-fp2x 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

serde_yml crate is unsound and unmaintainedGHSA-hhw4-xg65-fp2x

GHSA-hhw4-xg65-fp2x is a security vulnerability in serde_yml. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asRUSTSEC-2025-0068

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

🦀serde_yml

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

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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`serde_yml`	all versions	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 serde_yml, 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 serde_yml for GHSA-hhw4-xg65-fp2x. 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

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`](https://crates.io/crates/serde_norway) - Maintained fork of `serde_yaml`, using `unsafe-libyaml-norway` - [`serde_yaml_ng`](https://crates.io/crates/serde_yaml_ng) - Maintained fork of `serde_yaml`, using unmaintained `unsafe-libyaml` ## Incomplete pure Rust alternatives These

O3 Security · Impact-Aware SCA

Is GHSA-hhw4-xg65-fp2x in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works