Vulnerability in openclaw (CVE-2026-29609)
Summary
Vulnerability in openclaw (CVE-2026-29609). Risk of unauthorized operations or information disclosure. Exploitable via arrayBuffer. Mitigation: upgrade to 2026.2.14 or later.
Original description
The description as published by the source.
OpenClaw versions prior to 2026.2.14 contain a denial of service vulnerability in the fetchWithGuard function that allocates entire response payloads in memory before enforcing maxBytes limits. Remote attackers can trigger memory exhaustion by serving oversized responses without content-length headers to cause availability loss.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-29609 has been found in openclaw.
Attackers can target a specific entry point like arrayBuffer over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.2.14 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-29609" on the vendor's site.
CVE-2026-29609 (openclaw) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: arrayBuffer / maxBytes / openclaw / clawdbot
Patched: 2026.2.14 — 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 arrayBuffer without authentication.
Check the vendor advisory for the affected versions of openclaw. Attack surface: arrayBuffer / maxBytes / openclaw / clawdbot.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.2.14.
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade openclaw to 2026.2.14ステージング環境で 2026.2.14 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory vulncheck.com
- package github.com
- patch github.com