CVE-2026-53850

Description

### Summary Focus command could miss controlScope enforcement. In affected versions, a caller able to trigger the focus command could run the command without enforcing the expected control scope. 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 change focus state outside the intended caller authority. 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 restrict focus command access to trusted operators 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-53850

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

• —upgrade to 2026.4.25 or later

Is CVE-2026-53850 being exploited?

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

Affected packages (1)

• from 0, < 2026.4.25

CVSS scores

References (4)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2026-53850
• PATCHgithub.com/openclaw/openclaw
• WEBgithub.com/openclaw/openclaw/security/advisories/GHSA-mpc8-jxjh-qpgh
• WEBwww.vulncheck.com/advisories/openclaw-control-scope-enforcement-bypass-in-focus-command