{"answers":{"affected":"3 open source packages ship an affected version, including serde_yml.","exploited":"There is no known exploitation of GHSA-hhw4-xg65-fp2x in the wild and no public exploit code.","fix":"No fix has been published for GHSA-hhw4-xg65-fp2x yet. Limit exposure of the affected software until one is available.","what":"GHSA-hhw4-xg65-fp2x is a memory corruption vulnerability in serde_yml, published on 11 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-hhw4-xg65-fp2x and fix it if it is affected.\n\nWhat it is: GHSA-hhw4-xg65-fp2x is a memory corruption vulnerability in serde_yml, published on 11 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-hhw4-xg65-fp2x in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- serde_yml (crates.io): affected all versions up to 0.0.12; no fix listed\n- serde_yml (crates.io): affected all versions up to 0.0.12; no fix listed\n- serde_yml (crates.io): affected from 0.0.0-0; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-hhw4-xg65-fp2x/ (Markdown: https://insights.sbomify.com/GHSA-hhw4-xg65-fp2x/index.md)","id":"GHSA-hhw4-xg65-fp2x","markdown":"https://insights.sbomify.com/GHSA-hhw4-xg65-fp2x/index.md","name":"GHSA-hhw4-xg65-fp2x","record":{"aliases":["RUSTSEC-2025-0068"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust YAML library","requires_auth":"none","summary":"Unsoundness in serde_yml can cause segmentation faults, leading to denial of service; users should switch to maintained alternatives.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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)","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"serde_yml crate is unsound and unmaintained","id":"GHSA-hhw4-xg65-fp2x","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.0.12"],"package":"serde_yml","purl":null,"source":"GHSA-hhw4-xg65-fp2x"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["0.0.12"],"package":"serde_yml","purl":"pkg:cargo/serde_yml","source":"GHSA-hhw4-xg65-fp2x"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"serde_yml","purl":"pkg:cargo/serde_yml","source":"RUSTSEC-2025-0068"}],"products":null,"published":"2025-09-11","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Unsoundness in serde_yml can cause segmentation faults, leading to denial of service; users should switch to maintained alternatives.","url":"https://insights.sbomify.com/GHSA-hhw4-xg65-fp2x/"}