Resource Pressure Vulnerability in OpenClaw Voice-Call Package
Summary
GHSA-mfg5-7q5g-f37j: @openclaw/voice-call (and the bundled copy shipped in openclaw) accepted media-stream WebSocket upgrades before stream validation. Affects openclaw versions < 2026.2.22. Fixed in 2026.2.22. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
OpenClaw is an open-source library designed for building real-time voice call applications. It provides functionalities for managing media streams and WebSocket connections, enabling seamless communication between clients. The library includes the @openclaw/voice-call package, which is specifically focused on handling voice call media streams. However, a vulnerability was discovered that allows unauthenticated pre-start sockets to be held open, potentially leading to resource exhaustion in deployments where the media-stream endpoint is accessible.
Vulnerability Detail
The vulnerability arises from the @openclaw/voice-call package accepting media-stream WebSocket upgrades before validating the stream. This flaw creates a window where unauthenticated clients can open idle sockets, consuming connection-related resources. If exploited, this could lead to service degradation for legitimate users, as the system may become overwhelmed by the number of open connections. The vulnerability is classified with a CVSS score of 7.5, indicating a high severity risk.
How To Fix
Latest published version: 2026.10.6 as of 22 Oct 2026
npm install openclaw@2026.10.6
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2026.2.22
This is the first release that contains the fix.
npm install openclaw@2026.2.22
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary measure, you can implement a strict timeout for pre-start connections in your application. This can be done by closing sockets that do not send a valid 'start' frame within a specified timeframe. Additionally, consider limiting the number of connections per IP address to mitigate potential abuse.
Conclusion
The vulnerability in the OpenClaw voice-call package poses a significant risk to applications utilizing this library for real-time communication. By updating to the patched versions and implementing recommended workarounds, developers can mitigate the risk of resource exhaustion and ensure the stability of their services.
See every vulnerability recorded for openclaw →
FAQ
The vulnerability allows unauthenticated pre-start sockets to remain open, which can lead to resource exhaustion and service degradation.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The CVSS score for this vulnerability is 7.5, indicating a high severity risk.
If an immediate update is not possible, implement a strict timeout for pre-start connections and limit the number of connections per IP address as a temporary workaround.
You can find more information about OpenClaw and its functionalities on its official GitHub repository and documentation.
References
Related vulnerabilities
Recent vulnerabilities recorded for openclaw.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.