# CVE-2026-53832: OpenClaw < 2026.5.18 - Identity Header Forgery via Trusted-Proxy Configuration

> Local attackers can forge identity headers to assume operator identity and escalate privileges in OpenClaw when trusted-proxy configuration is enabled.

- **Severity:** High 7.4 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-rggc-m335-3wvj, MINI-cx8g-w386-4fgx, MINI-g6pw-2hcr-hqh7

## What is CVE-2026-53832?

CVE-2026-53832 is a high-severity authentication bypass vulnerability in Openclaw Openclaw, published on 12 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenClaw before 2026.5.18 contains an identity header validation vulnerability allowing local same-host callers to forge trusted-proxy identity headers. Attackers with access to the proxy-facing Gateway port can supply forged identity headers to assume operator identity and potentially escalate privileges.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

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


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

Products: Openclaw Openclaw.

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

Upgrade openclaw to 2026.5.18 or later.

## Is CVE-2026-53832 being exploited?

There is no known exploitation of CVE-2026-53832 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-53832 and fix it if it is affected.

What it is: CVE-2026-53832 is a high-severity authentication bypass vulnerability in Openclaw Openclaw, published on 12 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53832 in the wild and no public exploit code.

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

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-53832/ (Markdown: https://insights.sbomify.com/CVE-2026-53832/index.md)
```

## Sources

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

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