# CVE-2026-3691: OpenClaw Client PKCE Verifier Information Disclosure Vulnerability

> Remote attackers can disclose stored credentials by exploiting OAuth implementation flaws in OpenClaw, requiring user interaction to initiate the flow.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A: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:** 11 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-4h5x-fjp7-jhq3, GHSA-6g25-pc82-vfwp, MINI-gc9v-g8m8-g7wf, MINI-h3fx-7vf2-6852

## What is CVE-2026-3691?

CVE-2026-3691 is a medium-severity vulnerability in Openclaw Openclaw, published on 11 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 Client PKCE Verifier Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose stored credentials on affected installations of OpenClaw. User interaction is required to exploit this vulnerability in that the target must initiate an OAuth authorization flow.

The specific flaw exists within the implementation of OAuth authorization. The issue results from the exposure of sensitive data in the authorization URL query string. An attacker can leverage this vulnerability to disclose stored credentials, leading to further compromise. Was ZDI-CAN-29381.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


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

Products: Openclaw Openclaw.

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

Upgrade openclaw to 2026.2.25 or later.

## Is CVE-2026-3691 being exploited?

There is no known exploitation of CVE-2026-3691 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-3691 and fix it if it is affected.

What it is: CVE-2026-3691 is a medium-severity vulnerability in Openclaw Openclaw, published on 11 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-3691 in the wild and no public exploit code.

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

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-3691/ (Markdown: https://insights.sbomify.com/CVE-2026-3691/index.md)
```

## Sources

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

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