{"answers":{"affected":"1 open source package ship an affected version, including rtrb.","exploited":"There is no known exploitation of RUSTSEC-2026-0274 in the wild and no public exploit code.","fix":"Upgrade rtrb to a fixed version for your release line: 0.3.5 or 0.4.0.","what":"RUSTSEC-2026-0274 is an use after free vulnerability in rtrb, published on 4 Aug 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0274 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0274 is an use after free vulnerability in rtrb, published on 4 Aug 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0274 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rtrb (crates.io): affected from 0.0.0-0; fixed in 0.3.5, 0.4.0\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-0274/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0274/index.md)","id":"RUSTSEC-2026-0274","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0274/index.md","name":"RUSTSEC-2026-0274","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 ring buffer library","requires_auth":"none","summary":"A double free or use-after-free vulnerability in a Rust ring buffer library allows attackers to cause crashes or potentially execute code if element drops panic.","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":"`ReadChunk::commit` and `ReadChunk::commit_all` drop the committed elements\nbefore advancing the consumer head. If an element's `Drop` panics during the\ndrop loop, `head` is never advanced, so the ring buffer still treats those slots\nas holding live elements. When the `RingBuffer` is later dropped (it walks\n`head..tail` and drops each slot), or a subsequent `read_chunk()` / `commit()`\ntouches the same slots, the already-dropped elements are dropped a second time —\na double free (CWE-415) / use-after-free (CWE-416) reachable from safe Rust.\n\n## Mitigation\n\nUpdate to 0.3.5 (0.3.x line) or 0.4.0. Note that 0.4.0 contains a behavior\nchange in `is_abandoned()`, so users on 0.3.x should prefer 0.3.5.","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 / use-after-free in `ReadChunk::commit` when an element's `Drop` panics","id":"RUSTSEC-2026-0274","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.3.5","0.4.0"],"introduced":["0.0.0-0","0.4.0-0"],"last_affected":[],"package":"rtrb","purl":"pkg:cargo/rtrb","source":"RUSTSEC-2026-0274"}],"products":null,"published":"2026-08-04","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 or use-after-free vulnerability in a Rust ring buffer library allows attackers to cause crashes or potentially execute code if element drops panic.","url":"https://insights.sbomify.com/RUSTSEC-2026-0274/"}