UTC
High

OpenClaw's Trusted-proxy Control UI sessions retain privileged scopes without device identity on device-less allow paths

GHSA-48vw-m3qc-wr99 · published 2026-03-26 · updated 2026-04-22

Severity
High
CVSS score
Not scored
Chance of exploitation (EPSS)
No CVE
Fixed in
2026.3.22
What it is

Trusted-proxy Control UI sessions without device identity could retain self-declared privileged scopes on the device-less allow path.

What to do

Upgrade openclaw to 2026.3.22 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.

ccf16cd8892402022439346ae1d23352e3707e9e

Affected
PackageRegistryAffectedFixed in
openclawnpm< 2026.3.222026.3.22

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].