{"answers":{"affected":"1 open source package ship an affected version, including error-stack.","exploited":"There is no known exploitation of RUSTSEC-2026-0198 in the wild and no public exploit code.","fix":"Upgrade error-stack to 0.8.0 or later.","what":"RUSTSEC-2026-0198 is a memory corruption vulnerability in error-stack, published on 3 Jul 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0198 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0198 is a memory corruption vulnerability in error-stack, published on 3 Jul 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0198 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- error-stack (crates.io): affected from 0.0.0-0; fixed in 0.8.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-0198/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0198/index.md)","id":"RUSTSEC-2026-0198","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0198/index.md","name":"RUSTSEC-2026-0198","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust backtrace library","requires_auth":"none","summary":"A Rust library flaw allows aliased mutable references, causing undefined behavior and segmentation faults in applications using the affected crate.","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":"Affected versions of this crate return an iterator from\n`Report::frames_mut` whose `\u0026mut Frame` items have lifetimes independent\nof the iterator, so all yielded references can be held at the same time.\nA yielded frame's sources are also yielded by the iterator and reachable\nthrough the parent frame via `Frame::sources_mut`, allowing safe code to\nobtain two live mutable references to the same frame. This is undefined\nbehavior and can be used to cause a segmentation fault (see reproducer in\nthe linked issue). Versions 0.1.0 and 0.1.1 are affected through\n`Frame::source_mut` instead of `Frame::sources_mut`.\n\nThe flaw is fixed in 0.8.0 by replacing the iterator with internal\niteration: `Report::frames_mut` now takes a visitor closure, so mutable\naccess to a frame is scoped and cannot overlap with access to its\nsources.","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":"`Report::frames_mut` allows aliased mutable references","id":"RUSTSEC-2026-0198","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.8.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"error-stack","purl":"pkg:cargo/error-stack","source":"RUSTSEC-2026-0198"}],"products":null,"published":"2026-07-03","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 flaw allows aliased mutable references, causing undefined behavior and segmentation faults in applications using the affected crate.","url":"https://insights.sbomify.com/RUSTSEC-2026-0198/"}