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.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 03 Apr 2026 21:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OpenClaw < 2026.4.2 - PKCE Verifier Exposure via OAuth State Parameter | |
| First Time appeared |
Openclaw
Openclaw openclaw |
|
| Weaknesses | CWE-330 | |
| CPEs | cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:node.js:*:* | |
| Vendors & Products |
Openclaw
Openclaw openclaw |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-04-03T20:47:04.177Z
Reserved: 2026-03-30T13:51:47.549Z
Link: CVE-2026-34511
No data.
Status : Received
Published: 2026-04-03T21:17:11.517
Modified: 2026-04-03T21:17:11.517
Link: CVE-2026-34511
No data.
OpenCVE Enrichment
No data.
Weaknesses