Quick answers
- Is CVE-2026-53847 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53847 being exploited in the wild.
- How severe is CVE-2026-53847?
- Medium severity, with a CVSS score of 5.4, published 16 June 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,fixed=2026.5.6; Openclaw < 2026.5.6, <= 2026.5.5.
- Is there a fix for CVE-2026-53847?
- Yes. openclaw (npm): upgrade to 2026.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53847 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53847?
- 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.6 or later
npm install openclaw@2026.5.6
Technical details
An incorrect privilege assignment (CWE-266) exists in OpenClaw's Active Memory feature. In affected versions, a Gateway caller possessing 'operator.write' permissions can execute commands that mutate the global configuration, a capability that should be restricted to 'operator.admin' users. The vulnerability is reachable over the network if the Active Memory feature is enabled. An attacker with low-level authenticated access can exploit this to escalate their privileges regarding system configuration. The issue is addressed in version 2026.5.6.
Affected products
- openclaw openclaw <= 2026.5.5
Identifiers
- CVE-2026-53847
- GHSA-x629-46cc-7xgw
Timeline
- 2026-05-28: disclosed: Initial disclosure by researcher
- 2026-06-18: advisory: GitHub Advisory published
- 2026-05-28: patched: Version 2026.5.6 released