CVE-2026-34511 OpenClaw CVE debrief

Who should care

Users of OpenClaw prior to version 2026.4.2 should be aware of this vulnerability and take steps to mitigate it. This includes upgrading to the latest version of OpenClaw and ensuring that OAuth flows are properly secured. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability details and take necessary actions to protect their environments.

Technical summary

The vulnerability in OpenClaw before 2026.4.2 involves the improper use of the PKCE verifier in the Gemini OAuth flow. Specifically, the PKCE verifier is reused as the OAuth state parameter, which is exposed through the redirect URL. This exposure allows attackers to capture the redirect URL and obtain both the authorization code and PKCE verifier. As a result, the protection provided by PKCE is defeated, enabling attackers to redeem tokens. The affected product is OpenClaw, and the vulnerability is related to OAuth flows.

Defensive priority

Medium

Recommended defensive actions

• Upgrade to OpenClaw version 2026.4.2 or later
• Review and secure OAuth flows to prevent similar vulnerabilities
• Monitor for suspicious activity related to OAuth and token redemption
• Confirm whether affected OpenClaw deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record was published on 2026-04-03T21:17:11.517Z and last modified on 2026-07-24T22:10:00.140Z. The NVD entry is currently Analyzed. The source item URL for CVE-2026-34511 is available but details are limited. Defenders should verify the affected scope and severity with the official CVE record and vendor advisory.

Official resources