{"answers":{"affected":"1 open source package ship an affected version, including metacall.","exploited":"There is no known exploitation of RUSTSEC-2026-0156 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0156 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0156 is an use after free vulnerability in metacall, published on 1 Jun 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0156 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0156 is an use after free vulnerability in metacall, published on 1 Jun 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0156 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-0156/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0156/index.md)","id":"RUSTSEC-2026-0156","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0156/index.md","name":"RUSTSEC-2026-0156","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 library","requires_auth":"none","summary":"A use-after-free vulnerability in the Rust metacall library allows attackers to trigger a bad-free via the safe API, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`exception_struct` is a local stack variable, but the code passes its address to the C language as `\u0026mut exception_struct as *mut _ as *mut c_void`. Then, the returned `MetaCallException` value is stored here:\n```rust\nOk(Self {\n    exception_struct: Arc::new(exception_struct),\n    value: exception_ptr,\n    leak: false,\n})\n```\nBecause leak is false, the destructor will run later. But the original exception pointer points to Rust stack memory.\n\n## Trigger\n\n```rust\n#[test]\nfn exception_bad_free_safe_api() {\n    let original = metacall::MetaCallException::new(\n        \"test\",\n        \"test\",\n        \"test\",\n        1,\n    );\n\n    drop(original); // AddressSanitizer: bad-free\n}\n```\n\n## Impact\n\nEvery time the `MetaCallException` is created, when it is dropped, it leads to a bad-free. This can be triggered through the safe public API `MetaCallException::new()`, 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":"Bad-free in `MetaCallException::new`","id":"RUSTSEC-2026-0156","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"use_after_free","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-0156"}],"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":"A use-after-free vulnerability in the Rust metacall library allows attackers to trigger a bad-free via the safe API, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/RUSTSEC-2026-0156/"}