CVE-2026-35619: OpenClaw has a Gateway HTTP /v1/models Route Bypasses Operator Read Scope
Fixed in OpenClaw 2026.3.24, the current shipping release. Summary The OpenAI-compatible HTTP endpoint /v1/models accepts bearer auth but does not enforce operator method scopes. In contrast, the WebSocket RPC path enforces operator.read for models.list.
Published Mar 30, 2026 · Updated Apr 10, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.3.23
- Fixed in
- 2026.3.24
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Fixed in OpenClaw 2026.3.24, the current shipping release.
Summary
The OpenAI-compatible HTTP endpoint /v1/models accepts bearer auth but does not enforce operator method scopes.
In contrast, the WebSocket RPC path enforces operator.read for models.list.
A caller connected with operator.approvals (no read scope) is rejected for models.list (missing scope: operator.read) but can still enumerate model metadata through HTTP /v1/models.
Confirmed on current main at commit 06de515b6c42816b62ec752e1c221cab67b38501.
Details
The WS control-plane path enforces role/scope checks centrally before dispatching methods. For non-admin operators, this includes required method scopes such as operator.read for models.list.
The HTTP compatibility path for /v1/models performs bearer authorization and then returns model metadata; it does not apply an equivalent scope check.
As reproduced, a caller with only operator.approvals can:
- connect successfully,
- fail
models.listover WS withmissing scope: operator.read, - fetch
/v1/modelsover HTTP with status 200 and model data.
This is a cross-surface authorization inconsistency where the stricter WS policy can be bypassed via HTTP.
Impact
- Callers lacking
operator.readcan still enumerate gateway model metadata through HTTP compatibility routes. - Breaks scope model consistency between WS RPC and HTTP surfaces.
- Weakens least-privilege expectations for operators granted non-read scopes.
Patch Suggestion
1) Enforce read scope on /v1/models routes
Apply a scope gate equivalent to models.list before serving /v1/models or /v1/models/:id.
2) Reuse centralized scope-authorization helper for HTTP compatibility endpoints
Use the same operator scope logic used by WS dispatch (authorizeOperatorScopesForMethod(...)) to prevent policy drift.
3) Add regression tests
Keep this PoC and add explicit negative/positive controls:
operator.approvalswithout read is rejected on HTTP/v1/models.operator.readis accepted on both WSmodels.listand HTTP/v1/models.
Credit
Reported by @zpbrent.
Credited to zpbrent.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-68f8-9mhj-h2mp
- https://nvd.nist.gov/vuln/detail/CVE-2026-35619
- https://github.com/openclaw/openclaw/commit/06de515b6c42816b62ec752e1c221cab67b38501
- https://www.vulncheck.com/advisories/openclaw-authorization-bypass-via-http-v1-models-endpoint
- https://github.com/advisories/GHSA-68f8-9mhj-h2mp
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
