Rust advisories / rustyscript
Vulnerability MediumRUSTSEC-2024-0405 · rustyscript
RUSTSEC-2024-0405: op_panic in the base runtime can force a panic in the runtime's containing thread
Short answerA security vulnerability in the rustyscript crate: op_panic in the base runtime can force a panic in the runtime's containing thread. GitHub rates it Medium. Fixed in 0.6.1: update to a fixed version.
| Crate | rustyscript |
|---|---|
| Type | Vulnerability (denial-of-service) |
| Affected versions | From 0.3.1 before 0.6.1. |
| Fixed in | 0.6.1 |
| Severity | Medium (GitHub rating) |
| Published | 2024-07-18 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-fwfx-rrv8-crpf |
What to do
- See which version you have:
cargo tree -i rustyscript(it also shows which of your dependencies pulls it in). - Update within your version requirement:
cargo update -p rustyscript. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for examplerustyscript = "0.6.1") or update the dependency that pulls it in. - Check again with
cargo audit, or paste your Cargo.lock into our Cargo.toml checker.
Details from the advisory
Affected versions use deno_core releases that expose Deno.core.ops.op_panic to the JS runtime in the base core
This function when called triggers a manual panic in the thread containing the runtime.
It can be fixed by stubbing out the exposed op:
Deno.core.ops.op_panic = (msg) => { throw new Error(msg) };References
- Package: crates.io/crates/rustyscript
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0405.html
- Report: github.com/rscarson/rustyscript/issues/174
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?