Skip to main content
VulnerabilityPublished Updated

CVE-2026-34511: OpenClaw · Gemini OAuth exposed the PKCE verifier through the OAuth state parameter

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.0 High : upgrade to 2026.4.2 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.4.2
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.4.2.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.4.2
Fixed in
  • 2026.4.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in OpenClaw version 2026.4.2 and later, which separates the OAuth state parameter from the PKCE verifier. Users should upgrade to version 2026.4.2 or newer to remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

OpenClaw CLI versions up to 2026.4.1 have a vulnerability in the Gemini OAuth flow where the PKCE verifier is reused as the OAuth state parameter. This causes the verifier to be exposed in the redirect URL alongside the authorization code. An attacker who can capture the redirect URL could obtain both values, defeating the PKCE protection and enabling token redemption. The issue is fixed in version 2026.4.2 by separating the OAuth state from the PKCE verifier.

References

Community reviews

Loading reviews…