CVE-2026-34511: OpenClaw Gemini OAuth Exposed The PKCE Vulnerability

HIGH
Advisory Identifier: GHSA-9jpj-g8vv-j5mf
Share
CWE-345
Published
Advisory Summary

CVE-2026-34511 is a HIGH gemini oauth exposed the pkce vulnerability (CWE-345: Insufficient Verification of Data Authenticity) affecting OpenClaw libraries in the npm ecosystem. The issue involves gemini oauth exposed the pkce verifier through the oauth state parameter. Remediation is available by upgrading affected packages to version 2026.4.2.

CVE-2026-34511 at a Glance

CVE Identifier CVE-2026-34511
GHSA Identifier GHSA-9jpj-g8vv-j5mf
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-345: Insufficient Verification of Data Authenticity
Affected Product OpenClaw
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-34511

To remediate this vulnerability, upgrade all affected OpenClaw dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

openclaw fixed: 2026.4.2 
npm install openclaw@2026.4.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls openclaw

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-34511, inspect your project dependencies using npm:

npm ls openclaw

Analyze the terminal output to locate any version of OpenClaw in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.4.2), your application is affected.

Note: The npm ls openclaw command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-345: Insufficient Verification of Data Authenticity, where the product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. In OpenClaw, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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.

CVE-2026-34511 Affected OpenClaw Versions

1 component(s)
Fixed Versions:
2026.4.2
Product / Package Ecosystem Affected Versions Fixed Version
openclaw
npm/openclaw
npm
< 2026.4.2
2026.4.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/openclaw/openclaw/security/advisories/GHSA-9jpj-g8vv-j5mf
NVD — CVE-2026-34511 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-34511
Security Fix Commit FIX COMMIT
https://github.com/openclaw/openclaw/commit/a26f4d0f3ef0757db6c6c40277cc06a5de76c52f
OpenClaw Source Repository REPOSITORY
https://github.com/openclaw/openclaw
www.vulncheck.com/advisories/openclaw... WEB
https://www.vulncheck.com/advisories/openclaw-pkce-verifier-exposure-via-oauth-state-parameter

Frequently Asked Questions

What is CVE-2026-34511?
CVE-2026-34511 is a security vulnerability in OpenClaw involving Gemini OAuth exposed the PKCE verifier through the OAuth state parameter under CWE-345: Insufficient Verification of Data Authenticity.
Which OpenClaw versions are affected?
Affected versions include releases prior to 2026.4.2 across affected packages: openclaw.
What version fixes CVE-2026-34511?
Upgrading to 2026.4.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openclaw affected?
Yes, openclaw is affected in releases prior to 2026.4.2. Upgrade your dependency to 2026.4.2 or later.
What CWE is associated with CVE-2026-34511?
CVE-2026-34511 is classified under CWE-345: Insufficient Verification of Data Authenticity (The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.).
How can I check npm dependencies for CVE-2026-34511?
Run the dependency tree command: 'npm ls openclaw'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9jpj-g8vv-j5mf",
  "modified" : "2026-04-07T14:24:16Z",
  "published" : "2026-04-04T06:26:55Z",
  "aliases" : [ "CVE-2026-34511" ],
  "summary" : "OpenClaw: Gemini OAuth exposed the PKCE verifier through the OAuth state parameter",
  "details" : "## Summary\n\nBefore 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.\n\n## Impact\n\nAnyone 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.\n\n## Affected Packages / Versions\n\n- Package: `openclaw` (npm)\n- Affected versions: `<= 2026.4.1`\n- Patched versions: `>= 2026.4.2`\n- Latest published npm version: `2026.4.1`\n\n## Fix Commit(s)\n\n- `a26f4d0f3ef0757db6c6c40277cc06a5de76c52f` — separate OAuth state from the PKCE verifier\n\nOpenClaw thanks @BG0ECV for reporting.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "openclaw"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.4.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.4.1"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/security/advisories/GHSA-9jpj-g8vv-j5mf"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34511"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openclaw/openclaw/commit/a26f4d0f3ef0757db6c6c40277cc06a5de76c52f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openclaw/openclaw"
  }, {
    "type" : "WEB",
    "url" : "https://www.vulncheck.com/advisories/openclaw-pkce-verifier-exposure-via-oauth-state-parameter"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-345" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-04T06:26:55Z",
    "nvd_published_at" : null
  }
}