Quick answers
- Is CVE-2026-53845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53845 being exploited in the wild.
- How severe is CVE-2026-53845?
- Medium severity, with a CVSS score of 4.3, 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-53845?
- 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-53845 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53845?
- 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
A protection mechanism failure (CWE-693) exists in OpenClaw's skill-command dispatch logic. Specifically, certain dispatch paths fail to trigger the 'runBeforeToolCallHook', which is responsible for auditing and policy enforcement before a tool is executed. An authenticated attacker with network access can exploit this to run commands that bypass hook-based security controls. The vulnerability is addressed in version 2026.5.6; until then, users should avoid relying solely on hooks for enforcement and should narrow tool allowlists.
Affected products
- OpenClaw openclaw <= 2026.5.5
Identifiers
- CVE-2026-53845
- GHSA-68xw-r643-9p5w
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