Quick answers
- Is CVE-2026-53863 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53863 being exploited in the wild.
- How severe is CVE-2026-53863?
- High severity, with a CVSS score of 7.1, published 16 June 2026.
- Which products and versions are affected?
- openclaw (npm) SEMVER:introduced=0,fixed=2026.4.25; Openclaw < 2026.4.25, <= 2026.4.24.
- Is there a fix for CVE-2026-53863?
- Yes. openclaw (npm): upgrade to 2026.4.25 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53863 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-53863?
- 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.25 or later
npm install openclaw@2026.4.25
Technical details
A vulnerability classified as CWE-639 (Authorization Bypass Through User-Controlled Key) exists in OpenClaw's tool group policy resolver. The component fails to validate group IDs supplied by callers, allowing a user with low privileges to resolve policies for unvalidated groups. This can result in the application of incorrect group-policy decisions during tool invocation. The attack is reachable over the network but requires the 'affected feature' to be enabled and the attacker to have at least low-level authenticated access. The issue is addressed in version 2026.4.25.
Affected products
- openclaw openclaw <= 2026.4.24
Identifiers
- CVE-2026-53863
- GHSA-985f-72mj-8gf7
Timeline
- 2026-05-28: disclosed
- 2026-06-18: advisory
- 2026-04-25: patched