{"answers":{"affected":"1 open source package ship an affected version, including unicycle.","exploited":"There is no known exploitation of RUSTSEC-2026-0298 in the wild and no public exploit code.","fix":"Upgrade unicycle to 0.10.3 or later.","what":"RUSTSEC-2026-0298 is an use after free vulnerability in unicycle, published on 12 Sep 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0298 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0298 is an use after free vulnerability in unicycle, published on 12 Sep 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0298 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- unicycle (crates.io): affected from 0.0.0-0; fixed in 0.10.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-0298/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0298/index.md)","id":"RUSTSEC-2026-0298","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0298/index.md","name":"RUSTSEC-2026-0298","record":{"aliases":["GHSA-8gw6-724c-9h38"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust async library","requires_auth":"none","summary":"A use-after-free vulnerability in the Storage component allows attackers to cause memory corruption or crashes when a future's Drop implementation panics during container cleanup.","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":"`Storage::clear` walks the slab, empties each entry and frees the `Task`\nallocation once its reference count reaches zero. `self.tasks.set_len(0)` only\nruns after the loop.\n\nEmptying an entry drops the user future it holds, and `T` carries no bounds\nexcluding a panicking `Drop`. If one unwinds, the length is never committed and\n`self.tasks` still holds the pointers already processed. `Drop for Storage`\ncalls `clear` again, and the second pass dereferences `(*task.as_ptr()).entry`\non allocations the first pass already freed — a use-after-free (CWE-416)\nreachable from safe Rust.\n\n`Storage` is reached only through `Unordered`, whose `Drop` calls `clear`. No\nparticular method call is needed; dropping the container is enough.\n\n## Mitigation\n\nUpdate to 0.10.3.","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":"Use-after-free when a future's `Drop` panics while the container is dropped","id":"RUSTSEC-2026-0298","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":["0.10.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"unicycle","purl":"pkg:cargo/unicycle","source":"RUSTSEC-2026-0298"}],"products":null,"published":"2026-09-12","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 use-after-free vulnerability in the Storage component allows attackers to cause memory corruption or crashes when a future's Drop implementation panics during container cleanup.","url":"https://insights.sbomify.com/RUSTSEC-2026-0298/"}