# CVE-2026-32062: OpenClaw 2026.2.21-2 < 2026.2.22 - Unauthenticated WebSocket Resource Exhaustion via Media Stream

> Unauthenticated attackers can exhaust resources by holding idle WebSocket connections open, degrading service availability for legitimate users.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-mfg5-7q5g-f37j, MINI-pxjw-97jv-hrp8

## What is CVE-2026-32062?

CVE-2026-32062 is a high-severity denial of service vulnerability in Openclaw Openclaw, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw versions 2026.2.21-2 up to, but not including, 2026.2.22, and @openclaw/voice-call versions 2026.2.21 up to, but not including, 2026.2.22 accept media-stream WebSocket upgrades before stream validation, allowing unauthenticated clients to establish connections. Remote attackers can hold idle pre-authenticated sockets open to consume connection resources and degrade service availability for legitimate streams.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-32062?

4 open source packages ship an affected version, including @openclaw/voice-call and openclaw. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@openclaw/voice-call` | npm | All versions | 2026.2.22 |
| `@openclaw/voice-call` | npm | All versions | 2026.2.22 |
| `openclaw` | npm | All versions | 2026.2.22 |
| `openclaw` | npm | All versions | 2026.2.22 |

Products: Openclaw Openclaw, Openclaw Openclaw\/Voice-Call.

## How do I fix CVE-2026-32062?

Upgrade @openclaw/voice-call to 2026.2.22 or later.

## Is CVE-2026-32062 being exploited?

There is no known exploitation of CVE-2026-32062 in the wild and no public exploit code.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32062 and fix it if it is affected.

What it is: CVE-2026-32062 is a high-severity denial of service vulnerability in Openclaw Openclaw, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-32062 in the wild and no public exploit code.

Affected packages and fixed versions:
- @openclaw/voice-call (npm): affected all versions; fixed in 2026.2.22
- @openclaw/voice-call (npm): affected all versions; fixed in 2026.2.22
- openclaw (npm): affected all versions; fixed in 2026.2.22
- openclaw (npm): affected all versions; fixed in 2026.2.22

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32062/ (Markdown: https://insights.sbomify.com/CVE-2026-32062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32062
- OSV: https://osv.dev/vulnerability/CVE-2026-32062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32062/
Summaries are generated and may contain mistakes; the official description above is the record.