GHSA-2w8g-m5j8-7m87
Zalgo-like output that crashes the server
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@soketi/soketinpmDescription
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:
- Open an issue in the issues board
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @soketi/soketi | all versions | 0.26.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @soketi/soketi. 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.
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.
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.
How O3 protects you
O3 pinpoints whether GHSA-2w8g-m5j8-7m87 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-2w8g-m5j8-7m87. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2w8g-m5j8-7m87 in your dependencies?
O3 detects GHSA-2w8g-m5j8-7m87 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.