Not Failing Securely ('Failing Open') Affecting openclaw package, versions <2026.4.25
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-OPENCLAW-17393814
- published22 Jun 2026
- disclosed18 Jun 2026
- creditzsxsoft
Introduced: 18 Jun 2026
NewCVE-2026-53852 (opens in a new tab)How to fix?
Upgrade openclaw to version 2026.4.25 or higher.
Overview
openclaw is a 🦞 OpenClaw — Personal AI Assistant
Affected versions of this package are vulnerable to Not Failing Securely ('Failing Open') via the device re-pairing process when an empty scope set is provided. An attacker can gain broader access than intended by submitting a re-pairing request with an empty scope, which bypasses the intended containment guard. This is only exploitable if the affected feature is enabled and reachable, and if lower-trust input can access the re-pairing path.
Workaround
This vulnerability can be mitigated by revoking unexpected device sessions and requiring fresh pairing for suspicious devices until patched. Additionally, narrowing channel and tool allowlists, avoiding sharing one Gateway between mutually untrusted users, and disabling the affected feature when not needed can reduce risk.