dbcve.org
OpenclawApplication

CVE-2026-53850

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.4.25 or later.
See remediation →
57/100
Remediation priority · Elevated
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.25 contains a control scope enforcement bypass vulnerability in the focus command that allows authenticated callers to execute the command without proper authorization checks. Attackers can trigger the focus command to change focus state outside intended caller authority, potentially enabling unauthorized operations depending on gateway configuration and input trust levels.

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 version 2026.4.25 has a control scope enforcement bypass in the focus command. The vulnerability allows authenticated users to execute the focus command without proper authorization checks, enabling them to change focus state outside their intended caller authority scope. This is an access control bypass that could allow unauthorized operations depending on gateway configuration and trust levels.

MitigationUpgrade to OpenClaw version 2026.4.25 or later which contains the fix. Additionally, review and enforce proper authorization checks on the focus command to ensure callers can only change focus states within their authorized scope.

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.25= 2026.4.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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
    Run 'openclaw --version' or check the package manifest to identify the installed OpenClaw version
    Affected if Installed version is earlier than 2026.4.25 or exactly 2026.4.25
  2. Verify focus command availability
    Determine if the focus command is accessible to authenticated users in your environment by reviewing command documentation or attempting to invoke it
    Affected if The focus command is exposed and executable by authenticated users
  3. Inspect focus command authorization configuration
    Review the configuration files or access control settings that govern the focus command to determine if scope enforcement checks are defined
    Affected if No explicit authorization scope constraints are configured for the focus command or they are missing
  4. Review focus command usage logs
    Examine authentication and command execution logs for instances where the focus command was used, particularly checking for operations outside expected caller boundaries
    Affected if Logs show focus command execution occurring outside the caller's authorized scope
  5. Assess gateway trust configuration
    Inspect the gateway or API gateway configuration to determine trust levels between callers and the focus command execution context
    Affected if Gateway is configured with high trust levels that bypass scope validation for authenticated users

A user is affected if OpenClaw version is before 2026.4.25 AND the focus command is accessible to authenticated users without proper scope enforcement checks

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.25 or later
Fixed in 2026.4.25
Interim mitigation

Upgrade to OpenClaw version 2026.4.25 or later which contains the fix. Additionally, review and enforce proper authorization checks on the focus command to ensure callers can only change focus states within their authorized scope.

Recommended fix Moderate confidence

OpenClaw 2026.4.25 or later

  1. 1. Identify the current installed version of OpenClaw by checking the application or configuration files
  2. 2. Download OpenClaw version 2026.4.25 or a later stable release from the official repository (github.com)
  3. 3. Review release notes to confirm the security fix for the focus command authorization bypass is included
  4. 4. Create a backup of the current OpenClaw configuration and data directory
  5. 5. Stop the OpenClaw service or application
  6. 6. Install the upgraded version (2026.4.25 or later) following standard upgrade procedures
  7. 7. Verify the focus command now properly enforces authorization checks
  8. 8. Restart the OpenClaw service
Caveat Review release notes for any configuration changes or breaking changes between your current version and 2026.4.25

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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