Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦
📦 npm
Not in CISA KEV
CRITICAL severity

GHSA-g6w6-h933-4rc5 @soketi/soketi

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.

Soketi was exposed to Sandbox Escape vulnerability via vm2

Published
Aug 3, 2023
Updated
Aug 3, 2023
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
📦@soketi/soketi

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g6w6-h933-4rc5 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g6w6-h933-4rc5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-g6w6-h933-4rc5 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-g6w6-h933-4rc5: @soketi/soketi | O3 Security