{"answers":{"affected":"1 open source package ship an affected version, including owned-alloc.","exploited":"There is no known exploitation of RUSTSEC-2026-0291 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0291 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0291 is an use after free vulnerability in owned-alloc, published on 9 Sep 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0291 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0291 is an use after free vulnerability in owned-alloc, published on 9 Sep 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0291 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- owned-alloc (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/RUSTSEC-2026-0291/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0291/index.md)","id":"RUSTSEC-2026-0291","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0291/index.md","name":"RUSTSEC-2026-0291","record":{"aliases":[],"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 memory allocation library","requires_auth":"none","summary":"A double free and use-after-free vulnerability in OwnedAlloc allows attackers to cause memory corruption or crashes if a contained value's Drop implementation panics.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`OwnedAlloc::drop_in_place` destroys the contained value by hand, then commits\nthe ownership transfer with `mem::forget(self)` — which lives inside `into_raw`\nand so runs only after the destruction. `T::drop` is user code and may panic. If\nit does, the forget is skipped and the still-live `OwnedAlloc` unwinds, whose\ndestructor drops the same `T` a second time and then deallocates. For a `T` that\nowns an allocation, the same block is freed twice — a double free (CWE-415).\nThat destructor also reads the already-destroyed value through\n`Layout::for_value` before deallocating, a use-after-free (CWE-416).\n\n`MaybeUninitAlloc::drop_in_place` delegates to the same function, so both public\nentry points are affected. Storing a value whose `Drop` can panic and calling\neither is enough — no `unsafe` on the caller's side.\n\n## Fix\n\nNo fixed release is available. The crate has had no release since 2018 and the\nmaintainer has not responded to the report, nor to the one on `lockfree`, which\nis published from the same account. `forget_inner` leaks the value instead of\ndestroying it, which is safe.","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":"Double free in `OwnedAlloc::drop_in_place` when the contained value's `Drop` panics","id":"RUSTSEC-2026-0291","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"owned-alloc","purl":"pkg:cargo/owned-alloc","source":"RUSTSEC-2026-0291"}],"products":null,"published":"2026-09-09","related":[],"sources":[{"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":"A double free and use-after-free vulnerability in OwnedAlloc allows attackers to cause memory corruption or crashes if a contained value's Drop implementation panics.","url":"https://insights.sbomify.com/RUSTSEC-2026-0291/"}