CVE-2026-35619: Openclaw cli · OpenClaw has a Gateway HTTP /v1/models Route Bypasses Operator Read Scope
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2026.3.24 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.3.24
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade openclaw-cli to 2026.3.24.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenClaw version 2026.3.24. Operators should upgrade to this version or later to ensure that the HTTP /v1/models endpoint enforces the operator.read scope consistently with the WebSocket RPC path. The patch applies centralized scope authorization logic to HTTP routes to prevent this bypass. No additional mitigation actions are required beyond applying the official fix.
Description
OpenClaw CLI versions from 2026.1.29 up to but not including 2026.3.24 contain an authorization bypass vulnerability on the HTTP /v1/models endpoint. This endpoint accepts bearer tokens but does not enforce the required operator.read scope, unlike the WebSocket RPC path which correctly enforces scope checks. As a result, operators with only operator.approvals scope can enumerate model metadata via HTTP, bypassing intended access controls. This inconsistency weakens least-privilege enforcement for operators. The issue is fixed in OpenClaw 2026.3.24.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-68f8-9mhj-h2mp (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-35619 (opens in a new tab)
- github.com/openclaw/openclaw/commit/06de515b6c42816b62ec752e1c221cab67b38501 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-authorization-bypass-via-http-v1-models-endpoint (opens in a new tab)