CVE-2026-100578
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
Summary
OpenClaw (npm package openclaw) before 2026.7.1 fails to restrict owner-only infrastructure tools exposed through the chat.send endpoint. In Gateway deployments using authentication modes that honor caller identity and narrower operator scopes, a write-scoped non-owner caller can start a chat turn whose tool inventory includes the gateway and cron tools, causing the agent to invoke owner-only configuration or scheduling operations, including persistent state changes. Practical impact depends on the tools selected by the model and the caller's ability to steer the turn. Shared-secret token and password callers are treated as fully trusted operators under OpenClaw's security model and are outside the scope of this issue. The issue is fixed in 2026.7.1; as a workaround, restrict chat.send to administrators in identity-bearing deployments and remove gateway and cron from affected agent tool policies.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| OpenClaw | OpenClaw | 0 < 2026.7.1 | affected |
| OpenClaw | OpenClaw | 2026.7.1 | unaffected |
Weaknesses
- CWE-269: Improper Privilege Management
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-qw7m-h363-33qw
- https://www.vulncheck.com/advisories/openclaw-before-2026.7.1-authorization-bypass-via-chat-send
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.