dbcve.org
OpenclawApplication

CVE-2026-53844

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.4.29 or later.
See remediation →
71/100
Remediation priority · Elevated
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.4.29 contains a session visibility check bypass vulnerability in shared memory search that allows authenticated callers to access memory entries without proper authorization. Attackers can skip session visibility guards on the search path to retrieve memory entries that should not be visible to their session.

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 2026.4.29 contains a session visibility check bypass in shared memory search that allows authenticated attackers to circumvent session isolation guards and retrieve memory entries belonging to other sessions. The vulnerability exists in the search path logic where session visibility validation is improperly enforced or missing.

MitigationUpgrade to OpenClaw version 2026.4.29 or later to obtain the patched session visibility enforcement in shared memory operations. If upgrade is not immediately possible, review shared memory access controls and implement explicit session context validation before returning any memory entries.

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.4.29= 2026.4.29

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Identify OpenClaw version
    Locate and inspect the OpenClaw installation directory or use the product's version command (such as 'openclaw --version' or checking the software metadata). Compare the installed version against the affected range: versions < 2026.4.29 and = 2026.4.29.
    Affected if The installed version is any version before 2026.4.29, or exactly 2026.4.29.
  2. Confirm shared memory feature is in use
    Check if the OpenClaw deployment utilizes shared memory operations. Review the configuration files or runtime settings that enable or reference shared memory search functionality.
    Affected if Shared memory search functionality is enabled or configured in the environment.
  3. Verify session isolation configuration
    Inspect the session management or shared memory access control configuration files for the presence and correctness of session visibility validation rules. Look for any settings related to session context enforcement in memory operations.
    Affected if Session visibility validation is missing, disabled, or improperly configured in the shared memory access controls.

A user is affected if OpenClaw version is less than or equal to 2026.4.29, the shared memory search feature is enabled, and session visibility validation is not properly enforced in the configuration.

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.4.29 or later
Fixed in 2026.4.29
Interim mitigation

Upgrade to OpenClaw version 2026.4.29 or later to obtain the patched session visibility enforcement in shared memory operations. If upgrade is not immediately possible, review shared memory access controls and implement explicit session context validation before returning any memory entries.

Recommended fix Moderate confidence

2026.4.29

  1. 1. Identify the current installed version of OpenClaw by checking the application version or package manager
  2. 2. Create a full backup of the OpenClaw database and configuration files before proceeding with the upgrade
  3. 3. Upgrade OpenClaw to version 2026.4.29 or later using the appropriate package manager or installation method (e.g., pip install, apt-get, yum, or manual compilation)
  4. 4. After upgrading, restart the OpenClaw service to ensure the new version is active
  5. 5. Verify the upgrade was successful by checking that the version now shows 2026.4.29 or higher
  6. 6. Test the shared memory search functionality to confirm the session visibility check bypass has been resolved

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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