dbcve.org
OpenclawApplication

CVE-2026-41371

HIGH · 8.5 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 2026.3.28 or later.
See remediation →
91/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 chat.send that allows write-scoped gateway callers to trigger admin-only session reset operations. Attackers can rotate target sessions, archive prior transcript state, and force new session IDs without requiring admin scope by exploiting improper authorization checks in the chat.send path.

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 · moderate confidence

OpenClaw before 2026.3.28 has a privilege escalation vulnerability in chat.send where write-scoped gateway callers can trigger admin-only session reset operations. Attackers exploit improper authorization checks to rotate target sessions, archive transcript state, and force new session IDs without holding admin scope.

MitigationUpgrade to OpenClaw version 2026.3.28 or later, which implements proper authorization checks requiring admin scope for session reset operations in the chat.send path.

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
Changed
Confidentiality
None
Integrity
High
Availability
Low

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

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 installed OpenClaw version
    Run the version command for OpenClaw (typically 'openclaw --version' or check the package manifest) and compare it to the affected range: < 2026.3.28
    Affected if The installed version is before 2026.3.28
  2. Verify chat.send gateway endpoint is exposed
    Inspect the gateway configuration or API exposure settings to confirm the chat.send endpoint is accessible to gateway callers
    Affected if chat.send is exposed and accessible to non-admin gateway callers
  3. Confirm write-scoped gateway access is enabled
    Review the gateway authentication configuration to determine if write-scoped access tokens are permitted without admin scope verification
    Affected if Write-scoped tokens can access chat.send without admin scope validation
  4. Check session reset operation authorization
    Inspect the chat.send code path or configuration to verify whether session reset operations (rotate session, archive transcript, new session ID) enforce admin scope before execution
    Affected if Session manipulation operations bypass admin scope checks when triggered via chat.send

A user is affected if running OpenClaw version before 2026.3.28 with chat.send accessible to write-scoped gateway callers and no admin scope enforcement on session reset operations.

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 implements proper authorization checks requiring admin scope for session reset operations in the chat.send path.

Recommended fix Moderate confidence

2026.3.28

  1. 1. Identify the current installed version of OpenClaw by checking the application or deployment configuration
  2. 2. Upgrade OpenClaw to version 2026.3.28 or later to resolve the authorization bypass in chat.send
  3. 3. After upgrade, verify that the chat.send endpoint properly enforces admin scope for session reset operations
  4. 4. Test that write-scoped callers can no longer trigger admin-only session reset, rotate sessions, or force new session IDs without proper admin authorization
  5. 5. Review application logs to confirm the vulnerability is no longer exploitable

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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