dbcve.org
OpenclawApplication

CVE-2026-3691

MEDIUM · 5.3 CVSS v3.0 Published 2026-04-11
Fix available
A fix is available. Upgrade to 2026.2.25 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenClaw Client exposes the PKCE verifier in the OAuth authorization URL query string, allowing remote attackers who can intercept or access the authorization request to obtain this sensitive parameter. Since the PKCE verifier is meant to be kept secret and bound to the token exchange, its disclosure enables attackers to complete the authorization flow and steal stored credentials.

MitigationModify the OAuth implementation to prevent PKCE verifier exposure in URL query strings - typically by using POST-based authorization endpoints, ensuring proper state management, and implementing URL sanitization to prevent logging/exposure of sensitive parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenclawApplication
Affected:< 2026.2.25

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OpenClaw version
    Locate and inspect the installed OpenClaw version number (typically via --version flag, About dialog, or version file in the application directory)
    Affected if The installed version is before 2026.2.25
  2. Identify OAuth configuration
    Locate the OAuth client configuration file or settings where the authorization endpoint and flow are defined
    Affected if OAuth authorization is enabled and configured for user authentication
  3. Inspect authorization URL parameters
    Capture or review an authorization request URL generated by the client - examine the query string for a 'code_verifier' or 'code_challenge' parameter
    Affected if The PKCE verifier appears in the URL query string (not in the request body)
  4. Verify authorization request method
    Check whether the authorization request is sent via GET (URL query string) or POST (request body)
    Affected if Authorization requests use GET method with sensitive parameters in the URL
  5. Review logs for PKCE exposure
    Inspect application logs, debug output, or proxy traces for authorization request details
    Affected if Logs or network traces contain the PKCE verifier value in plain text

You are affected if OpenClaw version is below 2026.2.25 AND OAuth is configured, with the PKCE verifier visible in authorization URL query strings or logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2026.2.25 or later
Fixed in 2026.2.25
Interim mitigation

Modify the OAuth implementation to prevent PKCE verifier exposure in URL query strings - typically by using POST-based authorization endpoints, ensuring proper state management, and implementing URL sanitization to prevent logging/exposure of sensitive parameters.

Recommended fix Moderate confidence

2026.2.25 or later

  1. Upgrade OpenClaw to version 2026.2.25 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3691 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3691 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data