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

Zalgo-like output that crashes the serverGHSA-2w8g-m5j8-7m87

GHSA-2w8g-m5j8-7m87 is a security 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 Jan 10, 2022 · 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
3Kdownloads / week

Description

Impact

What kind of vulnerability is it? Who is impacted?

colors package caused zalgo-like output (see https://github.com/soketi/soketi/issues/276, https://github.com/Marak/colors.js/issues/289), breaking the servers.

Only NPM users that recently upgraded or installed the NPM package are affected.

Docker users seem to not be affected as the dependencies were bundled at the time of the build, which were tested.

Patches

Has the problem been patched? What versions should users upgrade to?

Latest patch. 0.26.1 to be exact at the time of writing.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

You cannot get around this as it's related to dependencies.

References

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

For more information

If you have any questions or comments about this advisory:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npm@soketi/soketiall versions0.26.1npm install @soketi/soketi@0.26.1

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 0.26.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2w8g-m5j8-7m87 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?_ [`colors`](https://npmjs.com/package/colors) package caused zalgo-like output (see https://github.com/soketi/soketi/issues/276, https://github.com/Marak/colors.js/issues/289), breaking the servers. **Only NPM users that recently upgraded or installed the NPM package are affected.** Docker users seem to not be affected as the dependencies were bundled at the time of the build, which were tested. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Latest patch. `0.26.1` to be exact at the time of
O3 Security · Impact-Aware SCA

Is GHSA-2w8g-m5j8-7m87 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Zalgo-like output that crashes the server