Rust advisories / js-sandbox
Vulnerability MediumRUSTSEC-2024-0403 · js-sandbox
RUSTSEC-2024-0403: op_panic in the base runtime can force a panic in the runtime's containing thread
Short answerA security vulnerability in the js-sandbox crate: op_panic in the base runtime can force a panic in the runtime's containing thread. GitHub rates it Medium. No fixed version: replace the crate or remove the affected code path.
| Crate | js-sandbox |
|---|---|
| Type | Vulnerability (denial-of-service) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | Medium (GitHub rating) |
| Published | 2024-07-18 |
| Last changed | 2025-10-28 |
| Also known as | GHSA-4mw5-2636-4535 |
What to do
- Find who pulls it in:
cargo tree -i js-sandbox. - Avoid the affected API, or replace the crate.
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, breaking sandboxing
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/js-sandbox
- Advisory: rustsec.org/advisories/RUSTSEC-2024-0403.html
- Report: github.com/Bromeon/js-sandbox/issues/31
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?