{"answers":{"affected":"1 open source package ship an affected version, including static_cell.","exploited":"There is no known exploitation of RUSTSEC-2025-0045 in the wild and no public exploit code.","fix":"Upgrade static_cell to 2.1.1 or later.","what":"RUSTSEC-2025-0045 is a vulnerability in static_cell, published on 17 Jul 2025."},"fix_prompt":"Check this codebase for RUSTSEC-2025-0045 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2025-0045 is a vulnerability in static_cell, published on 17 Jul 2025. \nExploitation: There is no known exploitation of RUSTSEC-2025-0045 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- static_cell (crates.io): affected from 2.0.1-0; fixed in 2.1.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-2025-0045/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0045/index.md)","id":"RUSTSEC-2025-0045","markdown":"https://insights.sbomify.com/RUSTSEC-2025-0045/index.md","name":"RUSTSEC-2025-0045","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["other"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust static cell library","requires_auth":"none","summary":"A Rust library allowed passing non-thread-safe values across threads, potentially causing undefined behavior or crashes in concurrent applications.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`ConstStaticCell\u003cT\u003e` could have been used to pass non-`Send` values to another thread, because `T` was not required to be `Send` while `ConstStaticCell` is `Send`.\n\nThis was corrected by introducing a `T: Send` bound.","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":"ConstStaticCell could have been used to pass non-Send values to another thread","id":"RUSTSEC-2025-0045","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["2.1.1"],"introduced":["2.0.1-0"],"last_affected":[],"package":"static_cell","purl":"pkg:cargo/static_cell","source":"RUSTSEC-2025-0045"}],"products":null,"published":"2025-07-17","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 allowed passing non-thread-safe values across threads, potentially causing undefined behavior or crashes in concurrent applications.","url":"https://insights.sbomify.com/RUSTSEC-2025-0045/"}