Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
RUSTSEC-2026-0157
metacallSeveral soundness violations exist in the Rust bindings for MetaCall, indicatively:
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.
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.
Same 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.
All issues can be triggered through safe public APIs.
Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.
No exploitation activity has been observed at this time. Continue routine monitoring.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard