{"answers":{"affected":"1 open source package ship an affected version, including salsa.","exploited":"There is no known exploitation of RUSTSEC-2026-0308 in the wild and no public exploit code.","fix":"Upgrade salsa to 0.28.5 or later.","what":"RUSTSEC-2026-0308 is an use after free vulnerability in salsa, published on 24 Sep 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0308 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0308 is an use after free vulnerability in salsa, published on 24 Sep 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0308 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- salsa (crates.io): affected from 0.23.0; fixed in 0.28.5\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-0308/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0308/index.md)","id":"RUSTSEC-2026-0308","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0308/index.md","name":"RUSTSEC-2026-0308","record":{"aliases":["GHSA-xc3w-55vh-cw3w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust incremental computation library","requires_auth":"none","summary":"Use-after-free in Salsa library allows attackers to expose memory or execute code via stale cached values.","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":"When an application reads an interned value's fields or uses that value as an input to a tracked function, Salsa must ensure that reusable storage has been validated for the current database revision. This prevents the value's fields and associated cached function results from being freed while in use. Affected versions checked this invariant only with `debug_assert!` when reading fields, and did not check it when using an interned value to access a tracked function's cached result.\n\nBugs in Salsa's dependency tracking, or an application-provided `Eq` implementation that incorrectly treats a changed query result as unchanged, can cause Salsa to reuse cached results containing stale interned values. If the application accesses these values and then interns additional values, Salsa can free the old fields or cached function results while references to them are still in use. This causes use-after-free through safe Rust APIs. Depending on the consuming application, attacker-controlled input may expose process memory or permit arbitrary code execution.\n\nThe fix asserts that an interned value's reusable storage has been validated for the current database revision before allowing an application to read its fields or access a tracked function's cached result using that value as input. If the assertion fails, Salsa panics before returning references to storage that could be freed while in use.\n\nSalsa 0.28.5 and newer address this vulnerability. Dependent applications should update Salsa and rebuild.\n\nApplications that disable garbage collection for all explicitly declared interned structs using `#[salsa::interned(revisions = usize::MAX)]` and do not use implicitly interned query arguments are not affected by this vulnerability.","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 in interned values and cached function results","id":"RUSTSEC-2026-0308","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.28.5"],"introduced":["0.23.0"],"last_affected":[],"package":"salsa","purl":"pkg:cargo/salsa","source":"RUSTSEC-2026-0308"}],"products":null,"published":"2026-09-24","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":"Use-after-free in Salsa library allows attackers to expose memory or execute code via stale cached values.","url":"https://insights.sbomify.com/RUSTSEC-2026-0308/"}