Quick answers
- Is CVE-2026-53850 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53850 being exploited in the wild.
- How severe is CVE-2026-53850?
- Medium severity, with a CVSS score of 5.5, 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-53850?
- 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-53850 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-53850?
- 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 missing authorization vulnerability (CWE-862) exists in the OpenClaw 'focus' command. The root cause is a failure to enforce the 'controlScope' check when the command is triggered, allowing a caller to execute the command outside of their intended authority. An attacker with local access and low privileges can exploit this to modify the focus state of the system. The vulnerability is addressed in version 2026.4.25. Mitigations include restricting access to the focus command to trusted operators and narrowing tool allowlists.
Affected products
- OpenClaw openclaw <= 2026.4.24
Identifiers
- CVE-2026-53850
- GHSA-mpc8-jxjh-qpgh
Timeline
- 2026-05-28: disclosed: Initial disclosure by reporter
- 2026-06-18: advisory: GitHub Advisory published
- 2026.4.25: patched: First stable patched version released