dbcve.org
OpenclawApplication

CVE-2026-41344

HIGH · 8.8 CVSS v3.1 Published 2026-04-23
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 before 2026.3.28 contains a privilege escalation vulnerability in the chat.send endpoint that allows write-scoped gateway callers to persist admin-only verboseLevel session overrides. Attackers can exploit the /verbose parameter to bypass access controls and expose sensitive reasoning or tool output intended to be restricted to administrators.

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 before version 2026.3.28 has a privilege escalation vulnerability in the chat.send API endpoint where the /verbose parameter allows write-scoped (non-admin) gateway callers to persist admin-only verboseLevel session overrides. This bypasses access controls and exposes sensitive reasoning or tool output intended only for administrators.

MitigationUpgrade to OpenClaw version 2026.3.28 or later which patches the access control bypass in the verbose parameter handling of the chat.send endpoint.

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

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Identify OpenClaw installation and version
    Locate the OpenClaw installation directory and check the version file or binary metadata. Common locations may include /opt/openclaw, /usr/local/openclaw, or the application root directory. Run: openclaw --version or check VERSION file in the installation directory.
    Affected if The installed version is lower than 2026.3.28 (e.g., 2026.3.27, 2026.2.15, etc.)
  2. Verify chat.send API endpoint availability
    Check if the chat.send API endpoint is exposed in the OpenClaw gateway. Review API routing configuration files (such as routes.json, api_config.yaml, or equivalent) to confirm the chat.send endpoint exists and is accessible.
    Affected if The chat.send endpoint is exposed and accessible to gateway callers
  3. Confirm non-admin access to /verbose parameter
    Examine the access control configuration (ACL, permissions, or role-based access settings) for the chat.send endpoint. Determine whether write-scoped or non-admin users are permitted to send requests with the /verbose parameter.
    Affected if Non-admin or write-scoped users can access and use the /verbose parameter in chat.send requests
  4. Check for persisted verboseLevel session overrides
    Review session storage, cache, or configuration files for any verboseLevel settings that may have been persisted. Look in session directories, database tables related to sessions, or configuration override files.
    Affected if Any verboseLevel session overrides exist that were set by non-admin users through the chat.send /verbose parameter

A user is affected if OpenClaw version is below 2026.3.28 AND the chat.send API endpoint with the /verbose parameter is accessible to non-admin users, allowing them to persist admin-only verboseLevel session overrides.

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.3.28 or later
Fixed in 2026.3.28
Interim mitigation

Upgrade to OpenClaw version 2026.3.28 or later which patches the access control bypass in the verbose parameter handling of the chat.send endpoint.

Recommended fix Moderate confidence

2026.3.28

  1. Upgrade OpenClaw to version 2026.3.28 or later to remediate the privilege escalation vulnerability in the chat.send endpoint

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41344 — 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-41344 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