Is CVE-2026-53865 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53865 being exploited in the wild.

How severe is CVE-2026-53865?

High severity, with a CVSS score of 7.1, published 16 June 2026.

Which products and versions are affected?

openclaw (npm) SEMVER:introduced=0,fixed=2026.5.2; Openclaw < 2026.5.2.

Is there a fix for CVE-2026-53865?

Yes. openclaw (npm): upgrade to 2026.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53865 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-53865?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53865: OpenClaw path traversal in maintenance task execution

Q: Is there a fix for CVE-2026-53865?

Yes. openclaw (npm): upgrade to 2026.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53865 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-53865?

Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53865 · Severity: high · CVSS 7.1 · Published 2026-06-16

OpenClaw, a workspace management tool, contains a vulnerability where maintenance tasks can be tricked into running unauthorized software. An attacker with local access could manipulate the system's search path to execute malicious code instead of the intended cleanup commands. This could lead to a full system compromise or unauthorized data access depending on the operator's configuration.

Technologies: openclaw (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-53865 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53865 being exploited in the wild.
How severe is CVE-2026-53865?: High severity, with a CVSS score of 7.1, published 16 June 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.5.2; Openclaw < 2026.5.2.
Is there a fix for CVE-2026-53865?: Yes. openclaw (npm): upgrade to 2026.5.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53865 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-53865?: Check whether you run openclaw (npm) or Openclaw at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

openclaw (npm): upgrade to 2026.5.2 or later
```
npm install openclaw@2026.5.2
```

Technical details

OpenClaw before version 2026.5.2 is vulnerable to an Untrusted Search Path (CWE-426) flaw. The root cause is that workspace-derived service PATH environment variables can influence the selection of the 'trash' executable during maintenance tasks. A local attacker with low privileges can manipulate these environment paths to point to a malicious executable, which is then executed by the system during maintenance operations. This allows for arbitrary command execution with the privileges of the OpenClaw operator. The issue is resolved in version 2026.5.2.

Affected products

OpenClaw openclaw < 2026.5.2

Identifiers

CVE-2026-53865
GHSA-rx78-29qr-5hq8

Timeline

2026-05-28: disclosed
2026-06-16: advisory: NVD/VulnCheck publication
2026-06-18: patched: GitHub Advisory updated with patch details

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.