CVE-2026-53852: OpenClaw < 2026.4.25 - Scope Bypass via Empty-Scope Device Re-pairing
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.
Other sources
OpenClaw before 2026.4.25 contains a scope containment bypass vulnerability in device re-pairing that allows authenticated operators to restore broader scopes than intended by submitting empty-scope re-pairing requests. Attackers can exploit this by sending re-pairing requests with empty scope sets to skip containment guards and retain unauthorized device access.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/openclawto a version that resolves this vulnerability.Fixed in 2026.4.25 - Configuration
Disable the device re-pairing feature in OpenClaw when it is not required to prevent empty-scope re-pairing bypasses.
OpenClaw device_repairing = disabled - Compensating control
Keep channel and tool allowlists narrow to limit which operators and plugins can initiate re-pairing or restore scopes.
- Compensating control
Avoid sharing a single Gateway between mutually untrusted users; isolate Gateways by trust boundary so operators cannot misuse shared Gateways to regain broader scopes.
- Operational
Revoke unexpected device sessions and require fresh pairing for suspicious devices until systems are patched to 2026.4.25.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-53852?
The severity of CVE-2026-53852 is low, rated at 2.3.
How do I fix CVE-2026-53852?
To fix CVE-2026-53852, update OpenClaw to version 2026.4.25 or later.
What is the impact of CVE-2026-53852?
CVE-2026-53852 can lead to a scope bypass during device re-pairing, potentially affecting containment.
Which software is affected by CVE-2026-53852?
CVE-2026-53852 affects OpenClaw Openclaw Node.js and other related OpenClaw components.
When was CVE-2026-53852 published?
CVE-2026-53852 was published on June 16, 2026.