GHSA-86ch-6w7v-v6xf is a high-severity (CVSS 7.5) CWE-755 vulnerability in @soketi/soketi. A fix is available for @soketi/soketi — see the affected versions and patch details below.
Denial of Service in soketi
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-86ch-6w7v-v6xf.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-86ch-6w7v-v6xf plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.
@soketi/soketinpmDescription
Impact
What kind of vulnerability is it? Who is impacted?
There was a wrong behavior when reading POST requests, making the server crash if it couldn't read the body. In case a POST request was sent to any endpoint of the server with an empty body, even unauthenticated with the Pusher Protocol, it would simply just crash the server for trying to send a response after the request closed.
All users that run the server are affected by it and it's highly recommended to upgrade to the latest patch.
Patches
Has the problem been patched? What versions should users upgrade to?
Updating to at least 0.24.1 or the latest version.
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
No. Upgrading is the only solution.
References
Are there any links users can visit to find out more?
https://github.com/soketi/soketi/releases/tag/0.24.1
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.24.1npm install @soketi/soketi@0.24.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @soketi/soketi to 0.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-86ch-6w7v-v6xf 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-86ch-6w7v-v6xf can be triaged on real exposure rather than presence alone.
Tailored to GHSA-86ch-6w7v-v6xf. 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-86ch-6w7v-v6xf in your dependencies?
O3 Security finds GHSA-86ch-6w7v-v6xf across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.