How severe is GHSA-g644-9gfx-q4q4?

GHSA-g644-9gfx-q4q4 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g644-9gfx-q4q4?

GHSA-g644-9gfx-q4q4 affects the following packages: vm2 (npm). Ecosystems affected: npm.

How do I fix GHSA-g644-9gfx-q4q4?

No patched version of vm2 has shipped for GHSA-g644-9gfx-q4q4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-g644-9gfx-q4q4 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vm2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g644-9gfx-q4q4 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-g644-9gfx-q4q4?

O3 pinpoints whether GHSA-g644-9gfx-q4q4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g644-9gfx-q4q4 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-g644-9gfx-q4q4, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-g644-9gfx-q4q4?

GHSA-g644-9gfx-q4q4 has an EPSS (Exploit Prediction Scoring System) score of 2.8%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g644-9gfx-q4q4?

GHSA-g644-9gfx-q4q4 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-g644-9gfx-q4q4 published, and has it been updated?

GHSA-g644-9gfx-q4q4 was published on July 13, 2023 and was last updated on November 4, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-g644-9gfx-q4q4

CRITICAL

vm2 Sandbox Escape vulnerability

Also known asCVE-2023-37903

Published

Jul 13, 2023

Updated

Nov 4, 2025

Affected

1 pkg

Patched

None yet

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

2.8%probability of exploitation in next 30 days

Lower Risk85th percentile-34.15%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

vm2npm

1.5Mdownloads / week

Description

In vm2 for versions up to 3.9.19, Node.js custom inspect function allows attackers to escape the sandbox and run arbitrary code.

Impact

Remote Code Execution, assuming the attacker has arbitrary code execution primitive inside the context of vm2 sandbox.

Patches

None.

Workarounds

None.

References

PoC is to be disclosed on or after the 5th of September.

Similarity with CVE-2023-37466

While this advisory might look similar to CVE-2023-37466, it is a completely different way of escaping the sandbox.

For more information

If you have any questions or comments about this advisory:

Open an issue in VM2

Thanks to Xion (SeungHyun Lee) of KAIST Hacking Lab for disclosing this vulnerability.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`vm2`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

vm2 is an open source vm/sandbox for Node.js. In vm2 for versions up to …

github.comGithubNov 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vm2. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of vm2 has shipped for GHSA-g644-9gfx-q4q4 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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.
How O3 protects you
O3 pinpoints whether GHSA-g644-9gfx-q4q4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g644-9gfx-q4q4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In vm2 for versions up to 3.9.19, Node.js custom inspect function allows attackers to escape the sandbox and run arbitrary code. ### Impact Remote Code Execution, assuming the attacker has arbitrary code execution primitive inside the context of vm2 sandbox. ### Patches None. ### Workarounds None. ### References PoC is to be disclosed on or after the 5th of September. ### Similarity with [CVE-2023-37466](https://nvd.nist.gov/vuln/detail/CVE-2023-37466) While this advisory might look similar to [CVE-2023-37466](https://nvd.nist.gov/vuln/detail/CVE-2023-37466), it is a completely different

O3 Security · Impact-Aware SCA

Is GHSA-g644-9gfx-q4q4 in your dependencies?

O3 detects GHSA-g644-9gfx-q4q4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works