Quick answers
- Is CVE-2026-53836 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53836 being exploited in the wild.
- How severe is CVE-2026-53836?
- High severity, with a CVSS score of 8.8, published 12 June 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,fixed=2026.5.12; Openclaw < 2026.5.12.
- Is there a fix for CVE-2026-53836?
- 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-53836 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-53836?
- 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
An allowlist bypass vulnerability exists in OpenClaw's PowerShell command parser due to incomplete input validation (CWE-184). The parser fails to recognize all valid abbreviated flag aliases for PowerShell's encoded-command parameter. A remote authenticated operator can exploit this by using unrecognized alias forms to submit arbitrary Base64-encoded PowerShell content that bypasses execution allowlist checks. This allows for arbitrary code execution on the host system within the context of the OpenClaw service. The issue is resolved in version 2026.5.12.
Affected products
- OpenClaw OpenClaw < 2026.5.12
Identifiers
- CVE-2026-53836
- GHSA-j472-gf56-x589
Timeline
- 2026-05-28: advisory: GitHub Security Advisory published
- 2026-06-12: disclosed: NVD publication and CVE assignment
- 2026-05-28: patched: Version 2026.5.12 released