{"answers":{"affected":"1 open source package ship an affected version, including auto_vec.","exploited":"There is no known exploitation of RUSTSEC-2026-0133 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0133 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0133 is a memory corruption vulnerability in auto_vec, published on 2 May 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0133 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0133 is a memory corruption vulnerability in auto_vec, published on 2 May 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0133 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- auto_vec (crates.io): affected from 0.0.0-0; no fix listed\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-0133/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0133/index.md)","id":"RUSTSEC-2026-0133","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0133/index.md","name":"RUSTSEC-2026-0133","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":"Invalid pointer arithmetic in iter APIs causes undefined behavior, potentially leading to memory corruption or crashes in Rust applications.","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 `iter()` and `iter_mut()` APIs compute\n`current = (\u0026children[0] as *const *const RawAutoChild).sub(1)`, which\nperforms pointer subtraction going before the start of the allocation. This\nis undefined behavior per Rust's pointer arithmetic rules.\n\nThis can be triggered through safe public APIs — `iter()` and `iter_mut()`\n— with no `unsafe` required from the caller.","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":false,"headline":"Invalid pointer arithmetic in `iter()` and `iter_mut()`","id":"RUSTSEC-2026-0133","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":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"auto_vec","purl":"pkg:cargo/auto_vec","source":"RUSTSEC-2026-0133"}],"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":"Invalid pointer arithmetic in iter APIs causes undefined behavior, potentially leading to memory corruption or crashes in Rust applications.","url":"https://insights.sbomify.com/RUSTSEC-2026-0133/"}