{"answers":{"affected":"1 open source package ship an affected version, including rustdx.","exploited":"There is no known exploitation of RUSTSEC-2026-0123 in the wild and no public exploit code.","fix":"Upgrade rustdx to 0.4.4 or later.","what":"RUSTSEC-2026-0123 is a memory corruption vulnerability in rustdx, published on 2 May 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0123 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0123 is a memory corruption vulnerability in rustdx, published on 2 May 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0123 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rustdx (crates.io): affected from 0.0.0-0; fixed in 0.4.4\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-0123/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0123/index.md)","id":"RUSTSEC-2026-0123","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0123/index.md","name":"RUSTSEC-2026-0123","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 bytes helper library","requires_auth":"none","summary":"Attackers can trigger undefined behavior and potential crashes or code execution by calling unsafe public functions with invalid slice positions.","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 `bytes_helper` module contains multiple public functions\n(`into_arr4()`, `into_arr2()`, `u8_from_le_bytes()`) that use\n`slice.get_unchecked(pos..pos + N)` without verifying that\n`pos + N \u003c= slice.len()`. These are public safe API functions, allowing any\ncaller to trigger undefined behavior by passing invalid positions.\n\nFor example, calling `into_arr4(\u0026data, 10)` where `data` is a 3-byte slice\ncauses an out-of-bounds access since position 10 exceeds the slice length.","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 in `bytes_helper` public safe functions","id":"RUSTSEC-2026-0123","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.4.4"],"introduced":["0.0.0-0"],"last_affected":[],"package":"rustdx","purl":"pkg:cargo/rustdx","source":"RUSTSEC-2026-0123"}],"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":"Attackers can trigger undefined behavior and potential crashes or code execution by calling unsafe public functions with invalid slice positions.","url":"https://insights.sbomify.com/RUSTSEC-2026-0123/"}