{"answers":{"affected":"3 open source packages ship an affected version, including libyml.","exploited":"There is no known exploitation of GHSA-gfxp-f68g-8x78 in the wild and no public exploit code.","fix":"No fix has been published for GHSA-gfxp-f68g-8x78 yet. Limit exposure of the affected software until one is available.","what":"GHSA-gfxp-f68g-8x78 is a memory corruption vulnerability in libyml, 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-gfxp-f68g-8x78 and fix it if it is affected.\n\nWhat it is: GHSA-gfxp-f68g-8x78 is a memory corruption vulnerability in libyml, 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-gfxp-f68g-8x78 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libyml (crates.io): affected from 0.0.0-0; no fix listed\n- libyml (crates.io): affected from 0.0.4 up to 0.0.5; no fix listed\n- libyml (crates.io): affected from 0.0.4 up to 0.0.5; 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-gfxp-f68g-8x78/ (Markdown: https://insights.sbomify.com/GHSA-gfxp-f68g-8x78/index.md)","id":"GHSA-gfxp-f68g-8x78","markdown":"https://insights.sbomify.com/GHSA-gfxp-f68g-8x78/index.md","name":"GHSA-gfxp-f68g-8x78","record":{"aliases":["RUSTSEC-2025-0067"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust YAML library","requires_auth":"none","summary":"Unsound memory handling in libyml allows attackers to trigger undefined behavior, potentially leading to code execution or crashes.","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":"In version 0.0.4, `libyml::string::yaml_string_extend` was revised resulting in undefined behaviour, which is unsound.\n\nThe GitHub project for `libyml` 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- [`libyaml-safer`](https://crates.io/crates/libyaml-safer) \n- [`unsafe-libyaml-norway`](https://crates.io/crates/unsafe-libyaml-norway) - Maintained fork of `unsafe-libyaml`","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":"`libyml::string::yaml_string_extend` is unsound and unmaintained","id":"GHSA-gfxp-f68g-8x78","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.0.0-0"],"last_affected":[],"package":"libyml","purl":"pkg:cargo/libyml","source":"RUSTSEC-2025-0067"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.4"],"last_affected":["0.0.5"],"package":"libyml","purl":null,"source":"GHSA-gfxp-f68g-8x78"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.4"],"last_affected":["0.0.5"],"package":"libyml","purl":"pkg:cargo/libyml","source":"GHSA-gfxp-f68g-8x78"}],"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":"Unsound memory handling in libyml allows attackers to trigger undefined behavior, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/GHSA-gfxp-f68g-8x78/"}