Is CVE-2026-53852 exploited in the wild?

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

How severe is CVE-2026-53852?

Medium severity, with a CVSS score of 5.4, published 16 June 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-53852?

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

How is CVE-2026-53852 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53852?

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-53852: OpenClaw scope containment bypass in device re-pairing

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

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

Q: How is CVE-2026-53852 attacked?

It is attacked over the network, in a software library.

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

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-53852 · Severity: medium · CVSS 5.4 · Published 2026-06-16

OpenClaw, a tool used for managing device gateways, contains a flaw in how it handles device re-pairing. An attacker could potentially bypass security restrictions to gain broader access permissions than intended. This could lead to unauthorized access to sensitive data or system functions depending on the specific configuration.

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

Quick answers

Is CVE-2026-53852 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53852 being exploited in the wild.
How severe is CVE-2026-53852?: Medium severity, with a CVSS score of 5.4, published 16 June 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.4.25; Openclaw < 2026.4.25, <= 2026.4.24.
Is there a fix for CVE-2026-53852?: Yes. openclaw (npm): upgrade to 2026.4.25 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53852 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53852?: 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.4.25 or later
```
npm install openclaw@2026.4.25
```

Technical details

A vulnerability exists in OpenClaw (npm package) where a device re-pairing request containing an empty scope set fails to trigger intended containment guards. This is a 'Failing Open' (CWE-636) issue where the system defaults to a less restrictive state when an empty scope is provided. An authenticated attacker with network access can exploit this during the re-pairing process to retain or restore scopes broader than those typically granted to the caller. The vulnerability is patched in version 2026.4.25.

Affected products

openclaw openclaw <= 2026.4.24

Identifiers

CVE-2026-53852
GHSA-8mg9-j9cf-54cj

Timeline

2026-05-28: disclosed
2026-06-18: advisory
2026.4.25: patched

References

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