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.
Blast Radius
@soketi/soketiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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.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.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 pinpoints whether GHSA-86ch-6w7v-v6xf 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-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 detects GHSA-86ch-6w7v-v6xf across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.