Zalgo-like output that crashes the server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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? - https://github.com/Marak/colors.js/issues/289 For more information If you have any questions or comments about this advisory: Open an issue in the issues board Email us at alex@renoki.org

Published by the source

12 Jan 2022, 21:45 UTC

Last modified by the source

11 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:16 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2w8g-m5j8-7m87

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2w8g-m5j8-7m87

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2w8g-m5j8-7m87

Advisory: Zalgo-like output that crashes the server
IDs: GHSA-2w8g-m5j8-7m87
Record: https://patchnext.com/advisories/ghsa-2w8g-m5j8-7m87 (revision 2, source checked 26 Oct 2026, 12:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @soketi/soketi 0.26.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @soketi/soketi: affected < 0.26.1; fixed in 0.26.1

## Suggested inspection (read-only)
- `npm ls @soketi/soketi --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @soketi/soketi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2w8g-m5j8-7m87 (OSV record GHSA-2w8g-m5j8-7m87 lists affected ranges: npm @soketi/soketi >=0 <0.26.1 (fixed))
- Verified: https://github.com/advisories/GHSA-2w8g-m5j8-7m87 (GitHub-reviewed advisory GHSA-2w8g-m5j8-7m87 lists affected ranges: npm @soketi/soketi >=0 <0.26.1)

Commands are suggestions: review each one before running it.