Quick answers
- Is CVE-2026-53844 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53844 being exploited in the wild.
- How severe is CVE-2026-53844?
- Medium severity, with a CVSS score of 6.5, published 16 June 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,fixed=2026.4.29; Openclaw < 2026.4.29, <= 2026.4.27.
- Is there a fix for CVE-2026-53844?
- Yes. openclaw (npm): upgrade to 2026.4.29 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53844 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53844?
- 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.29 or later
npm install openclaw@2026.4.29
Technical details
A missing authorization vulnerability (CWE-862) exists in the memory-wiki shared search component of OpenClaw. In affected versions, the search path fails to properly enforce session visibility guards. An authenticated attacker with network access and low privileges can exploit this to retrieve memory entries that should be restricted to other sessions. The vulnerability is specific to configurations where the shared memory search feature is enabled and reachable by lower-trust inputs. A fix is available in version 2026.4.29.
Affected products
- OpenClaw openclaw <= 2026.4.27
Identifiers
- CVE-2026-53844
- GHSA-72fw-cqh5-f324
Timeline
- 2026-05-28: disclosed
- 2026-06-18: advisory: GitHub Advisory published
- 2026-04-29: patched