{"answers":{"affected":"1 open source package ship an affected version, including circular-buffer.","exploited":"There is no known exploitation of RUSTSEC-2026-0256 in the wild and no public exploit code.","fix":"Upgrade circular-buffer to 2.0.1 or later.","what":"RUSTSEC-2026-0256 is an use after free vulnerability in circular-buffer, published on 11 Aug 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0256 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0256 is an use after free vulnerability in circular-buffer, published on 11 Aug 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0256 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- circular-buffer (crates.io): affected from 0.0.0-0; fixed in 2.0.1\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-0256/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0256/index.md)","id":"RUSTSEC-2026-0256","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0256/index.md","name":"RUSTSEC-2026-0256","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 circular buffer library","requires_auth":"none","summary":"A panic during element drop in circular-buffer causes use-after-free or double-free, potentially leading to 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":"Several methods in `circular-buffer` drop elements before updating the buffer's start/end metadata. If an element's `Drop` panics during the drop, the metadata update is skipped, so the buffer still treats the already-dropped elements as live. When the buffer is later dropped (or used after the panic is caught), those elements are visited again — a use-after-free / double-free reachable from safe Rust.\n\n## Impact\n\n- **CWE-415 (Double Free):** the same allocation is freed twice.\n- **CWE-416 (Use-After-Free):** a freed allocation is accessed during a repeated `Drop`.\n\nReachable entirely from safe Rust via `catch_unwind` with element types whose `Drop` can panic.\n\n## Fix\n\nFixed in `circular-buffer` 2.0.1 by adjusting the buffer's start/end metadata before the elements are dropped.","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":"Several methods in `circular-buffer` drop elements before updating the buffer's start/end metadata.","id":"RUSTSEC-2026-0256","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":["2.0.1"],"introduced":["0.0.0-0"],"last_affected":[],"package":"circular-buffer","purl":"pkg:cargo/circular-buffer","source":"RUSTSEC-2026-0256"}],"products":null,"published":"2026-08-11","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 panic during element drop in circular-buffer causes use-after-free or double-free, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/RUSTSEC-2026-0256/"}