Quick answers
- Is CVE-2026-53866 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53866 being exploited in the wild.
- How severe is CVE-2026-53866?
- High severity, with a CVSS score of 8.1, published 16 June 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,fixed=2026.5.12; Openclaw < 2026.5.12, <= 2026.5.10-beta.1.
- Is there a fix for CVE-2026-53866?
- Yes. openclaw (npm): upgrade to 2026.5.12 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53866 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53866?
- 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.5.12 or later
npm install openclaw@2026.5.12
Technical details
A vulnerability exists in OpenClaw's shell inline-command parsing logic (CWE-184). Due to an incomplete list of disallowed inputs or a logic error in the parser, specific command request forms can bypass the intended allowlist and approval mechanisms. An authenticated attacker with low privileges can exploit this over the network to execute arbitrary shell content without the required operator approval. The issue is fixed in version 2026.5.12. Mitigations include requiring manual approval for all shell inline-command forms and narrowing tool allowlists.
Affected products
- openclaw openclaw <= 2026.5.10-beta.1
Identifiers
- CVE-2026-53866
- GHSA-f397-5vjw-v2c2
Timeline
- 2026-05-28: disclosed
- 2026-06-18: advisory
- 2026-05-28: patched: First stable patched version is 2026.5.12