CVE-2026-34511: OpenClaw < 2026.4.2 - PKCE Verifier Exposure via OAuth State Parameter

Published Apr 3, 2026
·
Updated

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

- Package: openclaw (npm) - Affected versions: <= 2026.4.1 - Patched versions: >= 2026.4.2 - Latest published npm version: 2026.4.1

Fix Commit(s)

- a26f4d0f3ef0757db6c6c40277cc06a5de76c52f — separate OAuth state from the PKCE verifier

OpenClaw thanks @BG0ECV for reporting.

Other sources

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.

MITRE

Affected Software

2 affected componentsFixes available
npm/openclaw<=2026.4.1
2026.4.2
OpenClaw Openclaw Node.js<2026.4.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/openclaw to a version that resolves this vulnerability.

    Fixed in 2026.4.2
  2. Upgrade

    Upgrade npm/openclaw to a version that resolves this vulnerability.

    Fixed in 2026.4.2Patch a26f4d0f3ef0757db6c6c40277cc06a5de76c52f

Event History

Apr 3, 2026
CVE Published
via MITRE·08:45 PM
Data Sourced
via MITRE·08:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:17 PM
RemedyAffected Software
Apr 4, 2026
Advisory Published
via GitHub·06:26 AM
Data Sourced
via GitHub·06:26 AM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-34511?

CVE-2026-34511 is considered a medium severity vulnerability due to the potential exposure of sensitive information through the misuse of the OAuth state parameter.

2

How do I fix CVE-2026-34511?

To fix CVE-2026-34511, upgrade OpenClaw to version 2026.4.2 or later.

3

What does CVE-2026-34511 impact?

CVE-2026-34511 impacts OpenClaw versions prior to 2026.4.2 that utilize the Gemini OAuth flow.

4

What specific information is exposed by CVE-2026-34511?

CVE-2026-34511 allows for the potential exposure of the PKCE verifier via the OAuth state parameter reflected in the redirect URL.

5

Is CVE-2026-34511 related to OAuth security?

Yes, CVE-2026-34511 is related to OAuth security as it involves improper handling of the OAuth state parameter.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203