PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-34511 OpenClaw CVE debrief

CVE-2026-34511 is a vulnerability in OpenClaw before version 2026.4.2. The issue arises from the reuse of the PKCE verifier as the OAuth state parameter in the Gemini OAuth flow. This allows attackers who capture the redirect URL to obtain both the authorization code and PKCE verifier, effectively defeating PKCE protection and enabling token redemption. The vulnerability has a CVSS score of 6 and is classified as MEDIUM severity. Users of OpenClaw prior to version 2026.4.2 should be aware of this vulnerability and take steps to mitigate it.

Vendor
OpenClaw
Product
Unknown
CVSS
MEDIUM 6
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-03
Original CVE updated
2026-07-24
Advisory published
2026-04-03
Advisory updated
2026-07-24

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.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-34511 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-34511

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-34511 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-34511

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.