Vulnerability in openclaw (CVE-2026-32008)
Summary
Vulnerability in openclaw (CVE-2026-32008). Confidential information can be exposed externally. Exploitable via openclaw. Mitigation: upgrade to 2026.2.21 or later.
Original description
The description as published by the source.
Impact
assertBrowserNavigationAllowed() validated only http:/https: network targets but implicitly allowed other schemes. An authenticated gateway user could navigate browser sessions to file:// URLs and read local files via browser snapshot/extraction flows.
Affected Component
src/browser/navigation-guard.ts
Technical Reproduction
- Authenticate to a gateway that has browser tooling enabled.
- Invoke browser navigation with a
file://URL (for examplefile:///etc/passwd). - Read page content through browser snapshot/extract actions.
Demonstrated Impact
An attacker with valid gateway credentials and browser-tool access can exfiltrate local files readable by the OpenClaw process user (for example config/secrets in that user context).
Environment
- OpenClaw browser tool enabled
- Attacker has authenticated access capable of invoking browser actions
Remediation Advice
Reject unsupported navigation schemes and allow only explicitly safe non-network URLs. OpenClaw now blocks non-network schemes (such as file:, data:, and javascript:) while preserving about:blank.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.19-2 - Patched in planned next release:
2026.2.21
Fix Commit(s)
220bd95eff6838234e8b4b711f86d4565e16e401
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.21) so once npm 2026.2.21 is published, the advisory can be pub…
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-32008 has been found in openclaw.
Attackers can target a specific entry point like openclaw over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade openclaw to 2026.2.21 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-32008" on the vendor's site.
CVE-2026-32008 (openclaw) — CWE-610
Attack vector: remote (network-reachable) / no user interaction
Attack surface: openclaw / patched_versions
Patched: 2026.2.21 — 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-610) exists in openclaw. Attackers reach the vulnerable code path via openclaw.
Check the vendor advisory for the affected versions of openclaw. Attack surface: openclaw / patched_versions.
Severity: ?. Confidential information can be exposed externally.
Update to 2026.2.21.
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.21ステージング環境で 2026.2.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com