op_panic in the base runtime can force a panic in the runtime's containing threadGHSA-fwfx-rrv8-crpf
GHSA-fwfx-rrv8-crpf is a security vulnerability in rustyscript. A fix is available for rustyscript — see the affected versions and patch details below.
Real-World Exposure
rustyscriptReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
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) };
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | rustyscript | ≥ 0.4.0&&< 0.6.1 | 0.6.1cargo update -p rustyscript --precise 0.6.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rustyscript, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rustyscript to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fwfx-rrv8-crpf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-fwfx-rrv8-crpf in your dependencies?
Find it across crates.io, including transitive dependencies.