op_panic in the base runtime can force a panic in the runtime's containing thread
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- No fix listed
No CVSS vector from any source. Fix status from GitHub.
Summary
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: ```javascript Deno.core.ops.op_panic = (msg) => { throw new Error(msg) }; ```
Why it matters now
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | js-sandbox (crates.io) | up to 0.1.6 | — | No fix listed | GHSA-4mw5-2636-4535 |
- js-sandbox (crates.io) Vendor— Affected up to 0.1.6 Fixed in — No fix listed GHSA-4mw5-2636-4535
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-03 Threatist record created from GHSA-4mw5-2636-4535
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences