openclaw
Affected
- introduced
0, fixed2026.4.2(semver)
Fixed versions
2026.4.2
Fix
- Fixed version
2026.4.2npm install [email protected]
Advisory
Also known as: CVE-2026-34511
OpenClaw: Gemini OAuth exposed the PKCE verifier through the OAuth state parameter
Summary
Before OpenClaw 2026.4.2, the Gemini OAuth flow reused the PKCE verifier as the OAuth state value. Because the provider reflected state back in the redirect URL, the verifier could be exposed alongside the authorization code.
Impact
Anyone who could capture the redirect URL could learn both the authorization code and the PKCE verifier, defeating PKCE's interception protection for that flow and enabling token redemption.
Affected Packages / Versions
openclaw (npm)<= 2026.4.1>= 2026.4.22026.4.1Fix Commit(s)
a26f4d0f3ef0757db6c6c40277cc06a5de76c52f — separate OAuth state from the PKCE verifierOpenClaw thanks @BG0ECV for reporting.
High Basis: The source's own band: HIGH
0, fixed 2026.4.2 (semver)2026.4.2
2026.4.2npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0