{"answers":{"affected":"1 open source package ship an affected version, including metacall.","exploited":"There is no known exploitation of RUSTSEC-2026-0139 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0139 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0139 is a vulnerability in metacall, published on 2 May 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0139 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0139 is a vulnerability in metacall, published on 2 May 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0139 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-0139/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0139/index.md)","id":"RUSTSEC-2026-0139","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0139/index.md","name":"RUSTSEC-2026-0139","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"unknown","non_default_config":false,"product_category":"Rust MetaCall bindings","requires_auth":"none","summary":"Safe API misuse in Rust MetaCall bindings causes null-pointer dereference and double-free, leading to crashes or potential code execution.","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":"Two soundness violations exist in the Rust bindings for MetaCall:\n\n**Null-pointer dereference:** `MetaCallFuture::new_raw()` accepts a raw\npointer without validation. The `Debug` impl calls `Box::from_raw(self.data)`\non it. Passing a null pointer causes the `Debug` impl to construct a\n`NonNull` from null, producing undefined behavior.\n\n**Double-free:** `MetaCallPointer::clone()` shares the same `rust_value` raw\npointer between the clone and the original. Calling `get_value_untyped()` on\nboth clones calls `Box::from_raw` on the same pointer twice, resulting in a\ndouble-free.\n\nBoth issues can be triggered through safe public APIs —\n`MetaCallFuture::new_raw()`, `MetaCallPointer::new()`, `clone()`, and\n`get_value_untyped()` — 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":"Null-pointer dereference and double-free via safe APIs","id":"RUSTSEC-2026-0139","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":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"metacall","purl":"pkg:cargo/metacall","source":"RUSTSEC-2026-0139"}],"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":"Safe API misuse in Rust MetaCall bindings causes null-pointer dereference and double-free, leading to crashes or potential code execution.","url":"https://insights.sbomify.com/RUSTSEC-2026-0139/"}