Information Disclosure in openclaw (CVE-2026-3691)
Summary
Vulnerability in openclaw (CVE-2026-3691). Risk of unauthorized operations or information disclosure. Exploitable via code_verifier. Mitigation: upgrade to 2026.2.25 or later.
Original description
The description as published by the source.
Summary
The affected surface is the OpenClaw macOS app onboarding flow, and the macOS app is currently in beta.
In that beta onboarding flow, Anthropic OAuth used the PKCE code_verifier value as OAuth state, exposing that secret in front-channel URL state.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
<= 2026.2.24(latest published npm at triage time) - Affected surface: macOS app beta onboarding path (
apps/macos) - Not affected: core CLI/gateway onboarding paths
- Patched version :
2026.2.25
Impact
Scope is limited to the macOS beta onboarding OAuth path. Exploitation required obtaining both OAuth authorization artifacts and exposed state values during that flow.
Remediation
OpenClaw removed Anthropic OAuth sign-in from macOS onboarding and now supports setup-token-only Anthropic subscription auth in this path.
Fix Commit(s)
8f3310000a8b0c11eced054c2cdb6fb27803511a
Release Process Note
patched_versions is pre-set to the release (2026.2.25).
Advisory published with npm release 2026.2.25.2.25` is published, this advisory is published.
OpenClaw thanks @zdi-disclosures for reporting.
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-3691 has been found in openclaw.
Attackers can target a specific entry point like code_verifier over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade openclaw to 2026.2.25 or later.
If unsure, ask your IT team or search "openclaw CVE-2026-3691" on the vendor's site.
CVE-2026-3691 (openclaw) — CWE-200
Attack surface: code_verifier / state / openclaw / patched_versions
Patched: 2026.2.25 — 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.
Information disclosure (CWE-200) exists in openclaw. Attackers reach the vulnerable code path via code_verifier.
Check the vendor advisory for the affected versions of openclaw. Attack surface: code_verifier / state / openclaw / patched_versions.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.2.25.
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.25ステージング環境で 2026.2.25 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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