Summary
Zalgo-like output that crashes the server
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]
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Has the problem been patched? What versions should users upgrade to?
Latest patch. 0.26.1 to be exact at the time of writing.
Frequently Asked Questions
- What is GHSA-2W8G-M5J8-7M87? GHSA-2W8G-M5J8-7M87 is a critical-severity security vulnerability in @soketi/soketi (npm), affecting versions < 0.26.1. It is fixed in 0.26.1.
- Which versions of @soketi/soketi are affected by GHSA-2W8G-M5J8-7M87? @soketi/soketi (npm) versions < 0.26.1 is affected.
- Is there a fix for GHSA-2W8G-M5J8-7M87? Yes. GHSA-2W8G-M5J8-7M87 is fixed in 0.26.1. Upgrade to this version or later.
- Is GHSA-2W8G-M5J8-7M87 exploitable, and should I be worried? Whether GHSA-2W8G-M5J8-7M87 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2W8G-M5J8-7M87 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2W8G-M5J8-7M87? Upgrade
@soketi/soketito 0.26.1 or later.