CVE-2026-34511
Medium · 5.3CVSS
5.3
EPSS
0.4%
Published
Apr 3, 2026
CISA due date
—
The record
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.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| npm | openclaw | 0 | 2026.4.2 |
Related vulnerabilities
- GHSA-9jpj-g8vv-j5mf OpenClaw: Gemini OAuth exposed the PKCE verifier through the OAuth state parameter Same vulnerability
- GHSA-4hpg-mp64-x7xq OpenClaw: Internal/webchat command auth could inherit ownerAllowFrom wildcard state Also affects openclaw
- GHSA-8mg9-j9cf-54cj OpenClaw: Empty-scope device re-pairing could confuse caller scope containment Also affects openclaw
- GHSA-rx78-29qr-5hq8 OpenClaw: Workspace-derived service PATH could influence trash command selection Also affects openclaw
- GHSA-wc84-j36w-pw4x OpenClaw: Workspace .env STATE_DIRECTORY could influence bundled runtime dependency roots Also affects openclaw
- GHSA-cw4q-gqg5-g38h OpenClaw: Discord allowFrom could bind to mutable display names Also affects openclaw
- GHSA-mpc8-jxjh-qpgh OpenClaw: Focus command could miss controlScope enforcement Also affects openclaw
- GHSA-24vr-rprv-67rf OpenClaw: Workspace .env npm_execpath could influence bundled runtime dependency install Also affects openclaw