Quick answers
- Is CVE-2026-62229 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62229 being exploited in the wild.
- How severe is CVE-2026-62229?
- High severity, with a CVSS score of 8.8, published 17 July 2026.
- Which products and versions are affected?
- Openclaw < 2026.5.18.
- Is there a fix for CVE-2026-62229?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-62229 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-62229?
- Check whether you run 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.
Technical details
An authorization bypass vulnerability exists in OpenClaw's 'exec' allowlist glob matching logic. The root cause is improper limitation of pathnames (CWE-22) and incorrect authorization (CWE-863), where the system fails to properly neutralize special elements in input paths used for glob pattern matching. A remote attacker with low privileges can craft malicious input paths to traverse the allowlist and execute unauthorized commands or persist actions. This vulnerability is exploitable when the affected execution feature is enabled and reachable by lower-trust callers. The issue is resolved in version 2026.5.18.
Affected products
- OpenClaw OpenClaw < 2026.5.18
Timeline
- 2026-06-30: advisory: GitHub Security Advisory published
- 2026-07-16: advisory: VulnCheck advisory published
- 2026-07-17: disclosed: NVD publication date