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

> Untrusted web origins can bypass origin validation in trusted-proxy mode to gain privileged operator access, requiring an upgrade to fix.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-5wcw-8jjv-m286, MINI-4qvj-35w8-m5g9

## What is CVE-2026-32302?

CVE-2026-32302 is a high-severity authentication bypass vulnerability in Openclaw Openclaw, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenClaw is a personal AI assistant. Prior to 2026.3.11, browser-originated WebSocket connections could bypass origin validation when gateway.auth.mode was set to trusted-proxy and the request arrived with proxy headers. A page served from an untrusted origin could connect through a trusted reverse proxy, inherit proxy-authenticated identity, and establish a privileged operator session. This vulnerability is fixed in 2026.3.11.

Weakness: CWE-346 (Origin Validation Error)

## Which versions are affected by CVE-2026-32302?

2 open source packages ship an affected version, including openclaw. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openclaw` | npm | All versions | 2026.3.11 |
| `openclaw` | npm | All versions | 2026.3.11 |

Products: Openclaw Openclaw.

## How do I fix CVE-2026-32302?

Upgrade openclaw to 2026.3.11 or later.

## Is CVE-2026-32302 being exploited?

There is no known exploitation of CVE-2026-32302 in the wild and no public exploit code.

## Other vulnerabilities in Openclaw Openclaw

- [CVE-2026-28363](https://insights.sbomify.com/CVE-2026-28363/): Security feature bypass in OpenClaw (critical 9.9)
- [CVE-2026-30741](https://insights.sbomify.com/CVE-2026-30741/): Code injection in n/a (critical 9.8)
- [CVE-2026-33579](https://insights.sbomify.com/CVE-2026-33579/): OpenClaw < 2026.3.28 - Privilege Escalation via Missing Caller Scope Validation in Device Pair Approval (critical 9.4)
- [CVE-2026-32922](https://insights.sbomify.com/CVE-2026-32922/): OpenClaw < 2026.3.11 - Privilege Escalation via Unvalidated Scope in device.token.rotate (critical 9.4)
- [CVE-2026-32978](https://insights.sbomify.com/CVE-2026-32978/): OpenClaw < 2026.3.11 - Approval Bypass via Unrecognized Script Runners (critical 9.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32302 and fix it if it is affected.

What it is: CVE-2026-32302 is a high-severity authentication bypass vulnerability in Openclaw Openclaw, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32302 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.3.11
- openclaw (npm): affected all versions; fixed in 2026.3.11

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32302/ (Markdown: https://insights.sbomify.com/CVE-2026-32302/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32302
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32302
- OSV: https://osv.dev/vulnerability/CVE-2026-32302

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32302/
Summaries are generated and may contain mistakes; the official description above is the record.