CVE-2026-32062

@openclaw/voice-call (and the bundled copy shipped in openclaw) accepted media-stream WebSocket upgrades before stream validation. In reachable deployments, unauthenticated pre-start sockets could be held open and increase resource pressure.

Affected Packages / Versions

• openclaw (npm): vulnerable <= 2026.2.21-2, patched in 2026.2.22.
• @openclaw/voice-call (npm): vulnerable <= 2026.2.21, patched in 2026.2.22.

Technical Details

Before this fix, the voice-call media-stream path upgraded sockets first and ran shouldAcceptStream() after a later start frame. This created a pre-auth window where remote clients could hold idle sockets without call/token validation.

Fix Commit(s)

• 1d8968c8a821ff1a05c294a1846b3bcb6f343794

Release Process Note

patched_versions is pre-set to 2026.2.22 so this advisory is ready to publish once npm [email protected] and @openclaw/[email protected] are released.

OpenClaw thanks @jiseoung for reporting.

Availability risk in deployments where the media-stream endpoint is reachable and streaming is enabled. Under sustained abuse, this could consume connection-related resources and degrade service for legitimate streams.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-32062 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.22); upgrading removes the vulnerable code path.

Kodem intelligence

The fix adds layered controls in the media-stream path:

• strict pre-start timeout (close sockets that do not send a valid start frame quickly)
• global pending-connection cap
• per-IP pending-connection cap
• total open media-stream connection cap
• safer upgrade-path parsing in the webhook server

1. What is CVE-2026-32062? CVE-2026-32062 is a high-severity uncontrolled resource consumption vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
2. How severe is CVE-2026-32062? CVE-2026-32062 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-32062?
   • openclaw (npm) (versions < 2026.2.22)
   • @openclaw/voice-call (npm) (versions < 2026.2.22)
4. Is there a fix for CVE-2026-32062? Yes. CVE-2026-32062 is fixed in 2026.2.22. Upgrade to this version or later.
5. Is CVE-2026-32062 exploitable, and should I be worried? Whether CVE-2026-32062 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
6. What actually determines whether CVE-2026-32062 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.
7. How do I fix CVE-2026-32062?
   • Upgrade openclaw to 2026.2.22 or later
   • Upgrade @openclaw/voice-call to 2026.2.22 or later