NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

Soketi was exposed to Sandbox Escape vulnerability via vm2GHSA-g6w6-h933-4rc5

CRITICALFix: soketi/soketi#927

GHSA-g6w6-h933-4rc5 is a critical-severity (CVSS 9.8) vulnerability in @soketi/soketi. A fix is available for @soketi/soketi — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 3, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
@soketi/soketinpm
1Kdownloads / week

Description

Impact

What kind of vulnerability is it? Who is impacted? Anyone who might have used Soketi with the cluster driver (or through PM2).

Patches

Has the problem been patched? What versions should users upgrade to? Get the latest version of Soketi.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading? None. It's advised to upgrade to the latest version.

References

Are there any links users can visit to find out more?

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@soketi/soketiall versions1.6.0npm install @soketi/soketi@1.6.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @soketi/soketi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update @soketi/soketi to 1.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g6w6-h933-4rc5 is resolved across your whole dependency graph.

  3. 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

### Impact _What kind of vulnerability is it? Who is impacted?_ Anyone who might have used Soketi with the `cluster` driver (or through PM2). ### Patches _Has the problem been patched? What versions should users upgrade to?_ Get the latest version of Soketi. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ None. It's advised to upgrade to the latest version. ### References _Are there any links users can visit to find out more?_ - https://github.com/advisories/GHSA-cchq-frgv-rjh5 - https://github.com/patriksimek/vm2/issues/533 - https://gith
O3 Security · Impact-Aware SCA

Is GHSA-g6w6-h933-4rc5 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Soketi was exposed to Sandbox Escape vulnerability via…