CVE-2026-53852

Description

### Summary Empty-scope device re-pairing could confuse caller scope containment. In affected versions, a device re-pairing request with an empty scope set could skip the intended containment guard during re-pairing. This advisory is scoped to the named feature and configuration. It does not change OpenClaw's trusted-operator model: authenticated Gateway operators, installed plugins, and intentional local execution surfaces remain trusted unless a separate policy, approval, allowlist, sandbox, or auth boundary is crossed. ### Impact When the affected feature is enabled and reachable, this could restore or retain scopes broader than the caller should grant. Practical impact depends on the operator's configuration and whether lower-trust input can reach that path. ### Patched Versions The first stable patched version is `2026.4.25`. ### Mitigations revoke unexpected device sessions and require fresh pairing for suspicious devices until patched. As general hardening, keep channel and tool allowlists narrow, avoid sharing one Gateway between mutually untrusted users, and disable the affected feature when it is not needed.

How to fix CVE-2026-53852

To remediate CVE-2026-53852, upgrade the affected package to a fixed version below.

• —upgrade to 2026.4.25 or later

Is CVE-2026-53852 being exploited?

No exploitation signal available. Neither CISA KEV nor a current EPSS score has been published for CVE-2026-53852.

Affected packages (1)

• from 0, < 2026.4.25

CVSS scores

References (4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-53852
• PATCHgithub.com/openclaw/openclaw
• WEBgithub.com/openclaw/openclaw/security/advisories/GHSA-8mg9-j9cf-54cj
• WEBwww.vulncheck.com/advisories/openclaw-scope-bypass-via-empty-scope-device-re-pairing