{"answers":{"affected":"3 open source packages ship an affected version, including dyn-future.","exploited":"There is no known exploitation of GHSA-j3w3-p6mr-3hrh in the wild and no public exploit code.","fix":"No fix has been published for GHSA-j3w3-p6mr-3hrh yet. Limit exposure of the affected software until one is available.","what":"GHSA-j3w3-p6mr-3hrh is a memory corruption vulnerability in dyn-future, published on 21 Jan 2026."},"fix_prompt":"Check this codebase for GHSA-j3w3-p6mr-3hrh and fix it if it is affected.\n\nWhat it is: GHSA-j3w3-p6mr-3hrh is a memory corruption vulnerability in dyn-future, published on 21 Jan 2026. \nExploitation: There is no known exploitation of GHSA-j3w3-p6mr-3hrh in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dyn-future (crates.io): affected all versions up to 3.0.4; no fix listed\n- dyn-future (crates.io): affected all versions up to 3.0.4; no fix listed\n- dyn-future (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-j3w3-p6mr-3hrh/ (Markdown: https://insights.sbomify.com/GHSA-j3w3-p6mr-3hrh/index.md)","id":"GHSA-j3w3-p6mr-3hrh","markdown":"https://insights.sbomify.com/GHSA-j3w3-p6mr-3hrh/index.md","name":"GHSA-j3w3-p6mr-3hrh","record":{"aliases":["RUSTSEC-2026-0079"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust async library","requires_auth":"none","summary":"Unsound Drop implementation in DynFuture creates dangling references, potentially leading to memory corruption or crashes in Rust applications.","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":"DynFuture is unsound because its Drop implementation transmutes a trait-object reference into unrelated reference types, which constructs an invalid reference from trait object metadata.\n\nThis issue was reproduced against `dyn-future` 3.0.4 under Miri. And the crate is unmaintained.","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":"`DynFuture` drop can construct a dangling reference","id":"GHSA-j3w3-p6mr-3hrh","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["3.0.4"],"package":"dyn-future","purl":null,"source":"GHSA-j3w3-p6mr-3hrh"},{"ecosystem":"crates.io","fixed":[],"introduced":["0"],"last_affected":["3.0.4"],"package":"dyn-future","purl":"pkg:cargo/dyn-future","source":"GHSA-j3w3-p6mr-3hrh"},{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"dyn-future","purl":"pkg:cargo/dyn-future","source":"RUSTSEC-2026-0079"}],"products":null,"published":"2026-01-21","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 Drop implementation in DynFuture creates dangling references, potentially leading to memory corruption or crashes in Rust applications.","url":"https://insights.sbomify.com/GHSA-j3w3-p6mr-3hrh/"}