OpenclawApplication

CVE-2026-53865

HIGH · 7.1 CVSS v3.1 Published 2026-06-16
Fix available
A fix is available. Upgrade to 2026.5.26 or later.
See remediation →
73/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.5.2 contains a path traversal vulnerability in maintenance task execution that allows workspace-derived service paths to influence trash command selection. Attackers can execute unintended local executables from operator-unintended paths during maintenance operations by manipulating workspace-derived environment paths.

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.5.2 has a path traversal vulnerability in maintenance task execution where workspace-derived service paths influence trash command selection. Attackers can manipulate environment paths to execute unintended local executables from operator-unintended paths during maintenance operations.

MitigationUpgrade to OpenClaw 2026.5.2 or later which includes proper path validation to prevent traversal attacks in workspace-derived service paths.

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.5.26= 2026.5.26

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 installed OpenClaw version
    Run 'openclaw --version' or check the package manifest/binary metadata to determine the exact version number
    Affected if Version is less than 2026.5.2 or equals 2026.5.26
  2. Identify workspace-derived service path configuration
    Inspect OpenClaw configuration files (e.g., openclaw.conf, workspace.xml) for entries defining service paths, particularly those referencing workspace-relative or user-controlled paths
    Affected if Service paths are derived from or influenced by workspace configuration files
  3. Verify maintenance task execution is accessible
    Check if maintenance task functionality is enabled by examining config settings or CLI flags related to maintenance/trash operations (e.g., --maintenance, --cleanup, or similar)
    Affected if Maintenance task execution feature is enabled and operational
  4. Inspect environment variables influencing path selection
    Review environment variables such as PATH, OCLAW_SERVICE_PATH, WORKSPACE_PATH, or custom variables that OpenClaw may use to locate executables during maintenance operations
    Affected if Environment variables can be manipulated to inject alternate paths for trash command selection
  5. Review trash command configuration
    Examine logs, config, or runtime settings that define which trash/cleanup commands OpenClaw executes and from which paths those commands are sourced
    Affected if Trash command selection relies on workspace-influenced service paths without explicit path validation

Environment is affected if running OpenClaw version < 2026.5.2 or = 2026.5.26, workspace-derived service paths are in use, and maintenance operations that execute trash commands are performed.

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.

From vendor data
Upgrade available Upgrade to 2026.5.26 or later
Fixed in 2026.5.26
Interim mitigation

Upgrade to OpenClaw 2026.5.2 or later which includes proper path validation to prevent traversal attacks in workspace-derived service paths.

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-53865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-53865 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