UTC
High

OpenClaw: Untrusted web origins can obtain authenticated operator.admin access in trusted-proxy mode

CVE-2026-32302 · GHSA-5wcw-8jjv-m286 · published 2026-03-12 · updated 2026-03-16

Severity
High
CVSS score
8.1
Chance of exploitation (EPSS)
0.18%
Fixed in
2026.3.11
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

This issue affects deployments that expose the Gateway behind a trusted reverse proxy and rely on browser origin checks such as controlUi.allowedOrigins to restrict browser access. An attacker who can cause a victim browser to load a malicious page that can reach the proxy endpoint could establish a cross-site WebSocket connection and call privileged Gateway methods. In verified impact, the attacker-origin page was able to request operator.admin and successfully call config.get, exposing sensitive configuration. Depending on the deployment, the same authenticated operator path could also permit other privileged reads or mutations available to operator-class callers.

What to do

Upgrade openclaw to 2026.3.11 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

OpenClaw now enforces browser origin validation for any browser-originated WebSocket connection regardless of whether proxy headers are present. The fix shipped in [email protected]. Fixed commit: ebed3bbde1a72a1aaa9b87b63b91e7c04a50036b Release tag: v2026.3.11

If you cannot upgrade yet

Upgrade to 2026.3.11 or later. If you cannot upgrade immediately, avoid exposing browser-reachable Gateway WebSocket endpoints in trusted-proxy mode to untrusted origins, and ensure reverse-proxy/browser reachability is restricted to trusted origins only.

Affected
PackageRegistryAffectedFixed in
openclawnpm< 2026.3.112026.3.11

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].