{"answers":{"affected":"1 open source package ship an affected version, including scc.","exploited":"There is no known exploitation of RUSTSEC-2026-0205 in the wild and no public exploit code.","fix":"Upgrade scc to 3.8.4 or later.","what":"RUSTSEC-2026-0205 is an use after free vulnerability in scc, published on 6 Jul 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0205 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0205 is an use after free vulnerability in scc, published on 6 Jul 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0205 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- scc (crates.io): affected from 0.0.0-0; fixed in 3.8.4\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-0205/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0205/index.md)","id":"RUSTSEC-2026-0205","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0205/index.md","name":"RUSTSEC-2026-0205","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust array crate","requires_auth":"none","summary":"A Rust library's Array::insert method causes a double-free if the user-provided comparison function panics, potentially allowing code execution or crashes.","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":"In affected versions of this crate, `Array::insert` is not exception safe. In the `UPSERT` path, `key` and `value`'s snapshot is written to `self.data_block`, and after the insertion is completed, `key` and `value` are `mem::forget` in order to prevent double free. However, during the insertion, `K::compare` is invoked, which is a user-provided method. If user deliberately call panic in this function, during unwinding, the destructors of `key`, `value`, and `self` will all be called (since the `mem::forget` has not been called yet), leading to Double Free. Similar issues happens in the `!UPSERT` path.\n\nThe soundness issue was fixed in version `3.8.4` by using `ManuallyDrop` instead of `mem::forget`, and separating fallible code from infallible code during a node split - insert = insert_try -\u003e insert_unchecked.","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":"`Array::insert` violates exception safety if compare function panics, leading to potential Double-Free","id":"RUSTSEC-2026-0205","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":["3.8.4"],"introduced":["0.0.0-0"],"last_affected":[],"package":"scc","purl":"pkg:cargo/scc","source":"RUSTSEC-2026-0205"}],"products":null,"published":"2026-07-06","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 Rust library's Array::insert method causes a double-free if the user-provided comparison function panics, potentially allowing code execution or crashes.","url":"https://insights.sbomify.com/RUSTSEC-2026-0205/"}