{"answers":{"affected":"3 open source packages ship an affected version, including ruint.","exploited":"There is no known exploitation of GHSA-9fjq-45qv-pcm7 in the wild and no public exploit code.","fix":"Upgrade ruint to 1.17.1 or later.","what":"GHSA-9fjq-45qv-pcm7 is a memory corruption vulnerability in ruint, published on 22 Dec 2025."},"fix_prompt":"Check this codebase for GHSA-9fjq-45qv-pcm7 and fix it if it is affected.\n\nWhat it is: GHSA-9fjq-45qv-pcm7 is a memory corruption vulnerability in ruint, published on 22 Dec 2025. \nExploitation: There is no known exploitation of GHSA-9fjq-45qv-pcm7 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ruint (crates.io): affected all versions up to 1.17.0; no fix listed\n- ruint (crates.io): affected all versions up to 1.17.0; no fix listed\n- ruint (crates.io): affected from 0.0.0-0; fixed in 1.17.1\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-9fjq-45qv-pcm7/ (Markdown: https://insights.sbomify.com/GHSA-9fjq-45qv-pcm7/index.md)","id":"GHSA-9fjq-45qv-pcm7","markdown":"https://insights.sbomify.com/GHSA-9fjq-45qv-pcm7/index.md","name":"GHSA-9fjq-45qv-pcm7","record":{"aliases":["RUSTSEC-2025-0137"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust math library","requires_auth":"none","summary":"Attackers can trigger memory corruption in the ruint library via invalid inputs in release builds, 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":"The function `reciprocal_mg10` is marked as safe but can trigger undefined behavior (out-of-bounds access) because it relies on `debug_assert!` for safety checks instead of `assert!`.\n\nWhen compiled in release mode, the `debug_assert!` is optimized out, potentially allowing invalid inputs to cause memory corruption.","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":true,"headline":"ruint affected by unsoundness of safe `reciprocal_mg10`","id":"GHSA-9fjq-45qv-pcm7","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":["1.17.0"],"package":"ruint","purl":null,"source":"GHSA-9fjq-45qv-pcm7"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["1.17.0"],"package":"ruint","purl":"pkg:cargo/ruint","source":"GHSA-9fjq-45qv-pcm7"},{"ecosystem":"crates.io","fixed":["1.17.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"ruint","purl":"pkg:cargo/ruint","source":"RUSTSEC-2025-0137"}],"products":null,"published":"2025-12-22","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":"Attackers can trigger memory corruption in the ruint library via invalid inputs in release builds, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/GHSA-9fjq-45qv-pcm7/"}