{"answers":{"affected":"1 open source package ship an affected version, including caja.","exploited":"There is no known exploitation of RUSTSEC-2026-0130 in the wild and no public exploit code.","fix":"Upgrade caja to 0.3.0 or later.","what":"RUSTSEC-2026-0130 is a memory corruption vulnerability in caja, published on 2 May 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0130 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0130 is a memory corruption vulnerability in caja, published on 2 May 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0130 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- caja (crates.io): affected from 0.0.0-0; fixed in 0.3.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-0130/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0130/index.md)","id":"RUSTSEC-2026-0130","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0130/index.md","name":"RUSTSEC-2026-0130","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 library","requires_auth":"none","summary":"Out-of-bounds read/write in Caja indexing allows memory corruption and potential code execution via safe public APIs.","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":"The `Index` and `IndexMut` implementations for `Caja` use unchecked pointer\narithmetic without bounds validation. Creating a `Caja` with a small key and\nthen accessing an out-of-range index causes out-of-bounds reads or writes\nbeyond the allocated memory.\n\nThis can be triggered through safe public APIs — the `[]` indexing operator\non a `Caja` with an out-of-range index — with no `unsafe` required from the\ncaller.","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":"Out-of-bounds read/write in `Index` and `IndexMut` implementations","id":"RUSTSEC-2026-0130","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.3.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"caja","purl":"pkg:cargo/caja","source":"RUSTSEC-2026-0130"}],"products":null,"published":"2026-05-02","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":"Out-of-bounds read/write in Caja indexing allows memory corruption and potential code execution via safe public APIs.","url":"https://insights.sbomify.com/RUSTSEC-2026-0130/"}