Vulnerability in openclaw (CVE-2026-32062)
Summary
Vulnerability in openclaw (CVE-2026-32062). Risk of unauthorized operations or information disclosure. Exploitable via openclaw. Mitigation: upgrade to 2026.2.22 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-32062 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade openclaw to 2026.2.22 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-32062" on the vendor's site.
CVE-2026-32062 (openclaw) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: openclaw / start / patched_versions
Affected: <= 2026.2.21-2
Patched: 2026.2.22 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in openclaw. Attackers reach the vulnerable code path via openclaw without authentication.
Affected versions of openclaw: <= 2026.2.21-2. Attack surface: openclaw / start / patched_versions.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 2026.2.22. (If a vulnerable version <= 2026.2.21-2 is in production, plan an immediate maintenance window.)
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'openclaw' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'openclaw' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
openclawを grep し、稼働しているサービス・バージョンを把握する。 -
2Match against affected range verify
Confirm if version satisfies `<= 2026.2.21-2`Step 1 で見つかったバージョンが影響範囲
<= 2026.2.21-2に該当するか照合。本番で稼働中ならインシデント扱い。 -
3Apply patch patch
Upgrade openclaw to 2026.2.22ステージング環境で 2026.2.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory vulncheck.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com