{"answers":{"affected":"1 open source package ship an affected version, including cxx.","exploited":"There is no known exploitation of RUSTSEC-2026-0202 in the wild and no public exploit code.","fix":"Upgrade cxx to 1.0.195 or later.","what":"RUSTSEC-2026-0202 is an use after free vulnerability in cxx, published on 5 Jul 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0202 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0202 is an use after free vulnerability in cxx, published on 5 Jul 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0202 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- cxx (crates.io): affected from 0.0.0-0; fixed in 1.0.195\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-0202/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0202/index.md)","id":"RUSTSEC-2026-0202","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0202/index.md","name":"RUSTSEC-2026-0202","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 cxx bridge library","requires_auth":"none","summary":"Attackers can trigger use of uninitialized memory via panics in let_cxx_string!, potentially causing crashes or code execution in Rust applications using this crate.","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":"In affected versions of this crate, `let_cxx_string!` is not exception safe. After creating the `StackString`, if `match $value` panics, the content of `StackString` is not yet initialized, while the drop implementation of `StackString` unconditionally deinitializes the content, leading to use of uninitialized value.\n\nThe soundness issue was fixed in version `1.0.195` by moving drop logics to separate drop guard after initializing the `StackString`.","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":"`let_cxx_string!` uses uninitialized value due to exception safety violations","id":"RUSTSEC-2026-0202","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":["1.0.195"],"introduced":["0.0.0-0"],"last_affected":[],"package":"cxx","purl":"pkg:cargo/cxx","source":"RUSTSEC-2026-0202"}],"products":null,"published":"2026-07-05","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":"Attackers can trigger use of uninitialized memory via panics in let_cxx_string!, potentially causing crashes or code execution in Rust applications using this crate.","url":"https://insights.sbomify.com/RUSTSEC-2026-0202/"}