GHSA-hhw4-xg65-fp2x: Serde yml Serde_yml Crate Is Unsound And Vulnerability

MODERATE
CWE-787
Published
Advisory Summary

GHSA-hhw4-xg65-fp2x is a MODERATE serde_yml crate is unsound and vulnerability (CWE-787: Out-of-bounds Write) affecting Serde yml libraries in the crates.io ecosystem. The issue involves serde_yml crate is unsound and unmaintained. Remediation is available in the latest vendor maintenance releases.

GHSA-hhw4-xg65-fp2x at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-hhw4-xg65-fp2x
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-787: Out-of-bounds Write
Affected Product Serde yml
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-hhw4-xg65-fp2x

To remediate this vulnerability, upgrade all affected Serde yml dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

serde_yml fixed: Latest secure release
Upgrade serde_yml to Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for serde_yml

How to Check if You Are Affected

To determine whether your application is affected by GHSA-hhw4-xg65-fp2x, inspect your project dependencies for Serde yml:

inspect dependencies for serde_yml

Analyze the terminal output to locate any version of Serde yml in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-787: Out-of-bounds Write, where the product writes data past the end, or before the beginning, of the intended buffer. In Serde yml, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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 implementation do not rely on C `libyaml`. - [`serde_yaml2`](https://crates.io/crates/serde_yaml2) - [`yaml-peg`](https://crates.io/crates/yaml-peg)

GHSA-hhw4-xg65-fp2x Affected Serde yml Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
serde_yml
crates.io
≤ 0.0.12

References

Frequently Asked Questions

What is GHSA-hhw4-xg65-fp2x?
GHSA-hhw4-xg65-fp2x is a security vulnerability in Serde yml involving serde_yml crate is unsound and unmaintained under CWE-787: Out-of-bounds Write.
Which Serde yml versions are affected?
Affected versions include releases prior to current release patches across affected packages: serde_yml.
What version fixes GHSA-hhw4-xg65-fp2x?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is serde_yml affected?
Yes, serde_yml is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-hhw4-xg65-fp2x?
GHSA-hhw4-xg65-fp2x is classified under CWE-787: Out-of-bounds Write (The product writes data past the end, or before the beginning, of the intended buffer.).
How can I check crates.io dependencies for GHSA-hhw4-xg65-fp2x?
Run the dependency tree command: 'inspect dependencies for serde_yml'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-hhw4-xg65-fp2x",
  "modified" : "2025-09-15T13:58:35Z",
  "published" : "2025-09-15T13:58:35Z",
  "aliases" : [ ],
  "summary" : "serde_yml crate is unsound and unmaintained",
  "details" : "Using `serde_yml::ser::Serializer.emitter` can cause a segmentation fault, which is unsound.\n\nThe GitHub project for `serde_yml` was archived after unsoundness issues were raised.\n\nIf you rely on this crate, it is highly recommended switching to a maintained alternative.\n\n## Recommended alternatives\n\n- [`serde_norway`](https://crates.io/crates/serde_norway) - Maintained fork of `serde_yaml`, using `unsafe-libyaml-norway`\n- [`serde_yaml_ng`](https://crates.io/crates/serde_yaml_ng) - Maintained fork of `serde_yaml`, using unmaintained `unsafe-libyaml`\n\n## Incomplete pure Rust alternatives\n\nThese implementation do not rely on C `libyaml`.\n\n- [`serde_yaml2`](https://crates.io/crates/serde_yaml2)\n- [`yaml-peg`](https://crates.io/crates/yaml-peg)",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "serde_yml"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.0.12"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rustsec/advisory-db/issues/2395"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sebastienrousseau/serde_yml"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2025-0068.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-787" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-09-15T13:58:35Z",
    "nvd_published_at" : null
  }
}