Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9jpj-g8vv-j5mf | OpenClaw: Gemini OAuth exposed the PKCE verifier through the OAuth state parameter |
Mon, 06 Apr 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
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
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-04-06T16:57:09.160Z
Reserved: 2026-03-30T13:51:47.549Z
Link: CVE-2026-34511
Updated: 2026-04-06T16:56:57.771Z
Status : Analyzed
Published: 2026-04-03T21:17:11.517
Modified: 2026-04-22T18:03:16.207
Link: CVE-2026-34511
No data.
OpenCVE Enrichment
Updated: 2026-04-06T22:22:14Z
Github GHSA