CVE-2026-34511 OpenClaw < 2026.4.2 - PKCE Verifier Exposure via OAuth State Parameter
Attackers can capture OAuth redirect URLs to steal PKCE verifiers and authorization codes, bypassing PKCE protection to redeem tokens and take over accounts.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-34511?
CVE-2026-34511 is a medium-severity vulnerability in Openclaw Openclaw, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
OpenClaw before 2026.4.2 reuses the PKCE verifier as the OAuth state parameter in the Gemini OAuth flow, exposing it through the redirect URL. Attackers who capture the redirect URL can obtain both the authorization code and PKCE verifier, defeating PKCE protection and enabling token redemption.
Weakness: CWE-330
Which versions are affected by CVE-2026-34511?
2 open source packages ship an affected version, including openclaw. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
openclaw npm | All versions | 2026.4.2 |
openclaw npm | All versions | 2026.4.2 |
Products include Openclaw Openclaw.
How do I fix CVE-2026-34511?
Upgrade openclaw to 2026.4.2 or later.
Is CVE-2026-34511 being exploited?
There is no known exploitation of CVE-2026-34511 in the wild and no public exploit code.
Other vulnerabilities in Openclaw Openclaw
- CVE-2026-28363 Security feature bypass in OpenClaw
- CVE-2026-30741 Code injection in n/a
- CVE-2026-33579 OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval
- CVE-2026-32922 OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate
- CVE-2026-32978 OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners
Sources
Also known as GHSA-9jpj-g8vv-j5mf, MINI-r2mv-mw64-755x.