Rust advisories / crate
Security history · metacall · data from Oct 24, 2026
Is metacall safe to use? Its security history
VerdictOpen issue. 1 advisory has no fixed version yet; read RUSTSEC-2026-0156 before depending on it.
3advisories on record
1vulnerabilities
0unmaintained notices
nonenewest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0156 · 2026-06-01Bad-free in `MetaCallException::new`
- UnsoundRUSTSEC-2026-0157 · 2026-06-01Several memory corruption issues via safe APIs
- UnsoundRUSTSEC-2026-0139 · 2026-05-02Null-pointer dereference and double-free via safe APIs
Check your version
Run cargo tree -i metacall to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?