{"answers":{"affected":"1 open source package ship an affected version, including metacall.","exploited":"There is no known exploitation of RUSTSEC-2026-0157 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0157 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0157 is a memory corruption vulnerability in metacall, published on 1 Jun 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0157 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0157 is a memory corruption vulnerability in metacall, published on 1 Jun 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0157 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- metacall (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-0157/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0157/index.md)","id":"RUSTSEC-2026-0157","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0157/index.md","name":"RUSTSEC-2026-0157","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust MetaCall bindings","requires_auth":"none","summary":"Safe API misuse in Rust MetaCall bindings allows memory corruption via dangling pointers or invalid raw pointer dereferences, potentially leading to crashes or code execution.","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":"Several soundness violations exist in the Rust bindings for `MetaCall`, indicatively:\n\n**`MetaCallException::Clone`**: `Clone` is dangerous because it creates a second Rust object that still points to the same foreign `MetaCall` value, but does not actually own or keep that value alive. `value` is shallow copied and `leak=true` does not guarantee safety; `Clone` does not free the `MetaCall` value, but it still stores the same raw pointer. If the original is dropped, the `Clone` can retain a dangling pointer.\n\n**`MetaCallException::new_raw`**: is a safe function that accepts arbitrary raw pointer and dereferences C memory. This function is only correct if the caller gives it a valid, owned `MetaCall` value that must be destroyed by this wrapper. The method should be internal and not exposed to the public API or be declared as unsafe and be correctly documented.\n\nSame issues exist in `MetaCallThrowable::Clone`, `MetaCallThrowable::new_raw`, `MetaCallClass::Clone`, `MetaCallClass::new_raw`, `MetaCallFuture::Clone`, `MetaCallFuture::new_raw`, `MetaCallPointer::Clone`, `MetaCallPointer::new_raw`, `MetaCallFunction::Clone`, `MetaCallFunction::new_raw`, `MetaCallObject::Clone`, and `MetaCallObject::new_raw`. \n\nAll issues can be triggered through safe public APIs.","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":"Several memory corruption issues via safe APIs","id":"RUSTSEC-2026-0157","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":"metacall","purl":"pkg:cargo/metacall","source":"RUSTSEC-2026-0157"}],"products":null,"published":"2026-06-01","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":"Safe API misuse in Rust MetaCall bindings allows memory corruption via dangling pointers or invalid raw pointer dereferences, potentially leading to crashes or code execution.","url":"https://insights.sbomify.com/RUSTSEC-2026-0157/"}