Authorization Bypass Through User-Controlled Key Affecting openclaw package, versions <2026.7.1
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 applicationsSnyk Learn
Learn about Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JS-OPENCLAW-21708992
- published25 Oct 2026
- disclosed26 Sept 2026
- creditUnknown
Introduced: 26 Sep 2026
CVE-2026-100579 (opens in a new tab)How to fix?
Upgrade openclaw to version 2026.7.1 or higher.
Overview
openclaw is a 🦞 OpenClaw — Personal AI Assistant
Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key via message.action incorrectly trusting requester provenance. In identity-bearing Gateway deployments, a write-scoped caller can supply another sender's identifier to channel authorization checks and invoke a channel action under that spoofed requester identity, reaching operations the channel adapter would have denied to the real caller. The practical impact depends on the enabled channel, the action, and the target account's permissions.
Note: This is only exploitable in Gateway authentication modes that honor caller identity and narrower operator scopes. Shared-secret token and password callers are full trusted operators under OpenClaw's security model and are not affected.
Workaround
Restrict message.action access to administrators in identity-bearing deployments and disable sensitive channel actions that rely on requester identity.