{"answers":{"affected":"1 open source package ship an affected version, including rkyv.","exploited":"There is no known exploitation of RUSTSEC-2026-0001 in the wild and no public exploit code.","fix":"Upgrade rkyv to a fixed version for your release line: 0.7.46 or 0.8.13.","what":"RUSTSEC-2026-0001 is a vulnerability in rkyv, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0001 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0001 is a vulnerability in rkyv, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2026-0001 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rkyv (crates.io): affected from 0.0.0-0; fixed in 0.7.46, 0.8.13\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-0001/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0001/index.md)","id":"RUSTSEC-2026-0001","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0001/index.md","name":"RUSTSEC-2026-0001","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust serialization library","requires_auth":"none","summary":"Attackers can trigger undefined behavior and potential code execution or crashes by causing out-of-memory conditions during deserialization of shared pointers.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The `SharedPointer::alloc` implementation for `sync::Arc\u003cT\u003e` and `rc::Rc\u003cT\u003e` in `rkyv/src/impls/alloc/rc/atomic.rs` (and `rc.rs`) does not check if the allocator returns a null pointer on OOM (Out of Memory).\n\nThis null pointer can flow through to `SharedPointer::from_value`, which calls `Box::from_raw(ptr)` with the null pointer. This triggers undefined behavior when utilizing safe deserialization APIs (such as `rkyv::from_bytes` or `rkyv::deserialize_using`) if an OOM condition occurs during the allocation of the shared pointer.\n\nThe issue is reachable through safe code and violates Rust's safety guarantees.","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":"Potential Undefined Behaviors in `Arc\u003cT\u003e`/`Rc\u003cT\u003e` impls of `from_value` on OOM","id":"RUSTSEC-2026-0001","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.7.46","0.8.13"],"introduced":["0.0.0-0","0.8.0"],"last_affected":[],"package":"rkyv","purl":"pkg:cargo/rkyv","source":"RUSTSEC-2026-0001"}],"products":null,"published":"2026-01-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 undefined behavior and potential code execution or crashes by causing out-of-memory conditions during deserialization of shared pointers.","url":"https://insights.sbomify.com/RUSTSEC-2026-0001/"}