Skip to content
Web

CVE-2026-32062

8.7
High
EPSS 0.43%Patch availableMar 11, 2026

Unauthenticated WebSocket upgrade before validation enables DoS.

common questions

Is CVE-2026-32062 being exploited?

Not confirmed. CVE-2026-32062 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.43% probability of exploitation in the next 30 days.

How severe is CVE-2026-32062?

CVE-2026-32062 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-32062?

Yes. A fix has been recorded for CVE-2026-32062. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-32062 affect?

CVE-2026-32062 affects OpenClaw (versions 2026.2.21-2 before 2026.2.22), @openclaw/voice-call (versions 2026.2.21 before 2026.2.22). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-32062?

Upgrade to 2026.2.22+; enforce stream validation.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenClaw (versions 2026.2.21-2 before 2026.2.22)@openclaw/voice-call (versions 2026.2.21 before 2026.2.22)
impact

Resource exhaustion: idle pre-auth sockets can be kept open to degrade legitimate streams.

action required

Patch when possible

affected versions
openclaw openclaw
  • affected>= 2026.2.21-2 and < 2026.2.22
vendor says fixed in2026.2.22
openclaw voice-call
  • affected2026.2.21
vendor says fixed in2026.2.22

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free