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

> Attackers can capture OAuth redirect URLs to steal PKCE verifiers and authorization codes, bypassing PKCE protection to redeem tokens and take over accounts.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Apr 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-9jpj-g8vv-j5mf, MINI-r2mv-mw64-755x

## What is CVE-2026-34511?

CVE-2026-34511 is a medium-severity vulnerability in Openclaw Openclaw, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2026-34511?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.4.2 |
| `openclaw` | npm | All versions | 2026.4.2 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-34511?

Upgrade openclaw to 2026.4.2 or later.

## Is CVE-2026-34511 being exploited?

There is no known exploitation of CVE-2026-34511 in the wild and no public exploit code.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34511 and fix it if it is affected.

What it is: CVE-2026-34511 is a medium-severity vulnerability in Openclaw Openclaw, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-34511 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.4.2
- openclaw (npm): affected all versions; fixed in 2026.4.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34511/ (Markdown: https://insights.sbomify.com/CVE-2026-34511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34511
- OSV: https://osv.dev/vulnerability/CVE-2026-34511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34511/
Summaries are generated and may contain mistakes; the official description above is the record.