{"answers":{"affected":"1 open source package ship an affected version, including stack_collections.","exploited":"There is no known exploitation of RUSTSEC-2026-0301 in the wild and no public exploit code.","fix":"Upgrade stack_collections to 0.3.3 or later.","what":"RUSTSEC-2026-0301 is a memory corruption vulnerability in stack_collections, published on 22 Sep 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0301 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0301 is a memory corruption vulnerability in stack_collections, published on 22 Sep 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0301 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- stack_collections (crates.io): affected from 0.3.0; fixed in 0.3.3\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-0301/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0301/index.md)","id":"RUSTSEC-2026-0301","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0301/index.md","name":"RUSTSEC-2026-0301","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":true,"product_category":"Rust StackVec library","requires_auth":"none","summary":"A double-free vulnerability in StackVec::retain allows attackers to cause memory corruption or crashes if a panic occurs during element removal.","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":"## Summary\n\n`StackVec::retain` committed its new length to `self.len` only after\nits internal loop completed. If the retain predicate or a removed\nelement's `Drop` implementation panicked before the loop finished,\nunwinding proceeded with `self.len` still equal to the original,\npre-retain length, leaving either a duplicated or already-destroyed\nelement inside `0..len`. `StackVec`'s own `Drop` then revisited that\nslot, causing a double-drop (and for heap-owning types, a double-free).\n\n## Impact\n\nAffects `StackVec\u003cT, CAP\u003e::retain` for `T: Drop` types where the\npredicate or the removed element's destructor can panic, on builds\nwith unwinding enabled (`panic = \"unwind\"`). `no_std`/`panic = \"abort\"`\nbuilds cannot trigger this, since unwinding never occurs.\n\n## Patch\n\nFixed in 0.3.3 using an unwind-safe backshift guard, matching the\napproach `alloc::vec::Vec::retain` uses.","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":"Double free in `StackVec::retain` when a predicate or element `Drop` panics","id":"RUSTSEC-2026-0301","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.3.3"],"introduced":["0.3.0"],"last_affected":[],"package":"stack_collections","purl":"pkg:cargo/stack_collections","source":"RUSTSEC-2026-0301"}],"products":null,"published":"2026-09-22","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 vulnerability in StackVec::retain allows attackers to cause memory corruption or crashes if a panic occurs during element removal.","url":"https://insights.sbomify.com/RUSTSEC-2026-0301/"}