# CVE-2026-25253: OpenClaw/Clawdbot has 1-Click RCE via Authentication Token Exfiltration From gatewayUrl

> OpenClaw automatically connects to attacker-controlled WebSocket URLs via query parameters, leaking tokens and enabling server-side request forgery.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 1 Feb 2026
- **Updated:** 3 Feb 2026
- **Also known as:** GHSA-g8p2-7wf7-98mq

## What is CVE-2026-25253?

CVE-2026-25253 is a high-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 1 Feb 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 (aka clawdbot or Moltbot) before 2026.1.29 obtains a gatewayUrl value from a query string and automatically makes a WebSocket connection without prompting, sending a token value.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `clawdbot` | npm | All versions | 2026.1.29 |
| `clawdbot` | npm | All versions | 2026.1.29 |

Products: Openclaw Openclaw.

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

Upgrade clawdbot to 2026.1.29 or later.

## Is CVE-2026-25253 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25253 exists.

Public exploit code:

- Clawdbot/Moltbot/OpenClaw One-click RCE PoC 🦞 (CVE-2026-25253) (github_poc): https://github.com/ethiack/moltbot-1click-rce
- Proactive security monitoring for OpenClaw deployments. Detects ClawHavoc, AMOS stealer, CVE-2026-25253, memory poisoning, and supply chain attacks. (github_poc): https://github.com/adibirzu/openclaw-security-monitor
- PoC for CVE-2026-25253: one-click RCE in OpenClaw (Moltbot/Clawdbot) via token theft and cross-site WebSocket hijacking (github_poc): https://github.com/al4n4n/CVE-2026-25253-research
- > OpenClaw security audit and hardened deployment guide — known vulnerabilities (CVE-2026-25253, malicious skills, credential leakage), architectural mitigations, and a step-by-step VPS deployment plan (github_poc): https://github.com/FrigateCaptain/openclaw_vulnerabilities_and_solutions
- OpenClaw Authentication Token Exfiltration (github_poc): https://github.com/EQSTLab/CVE-2026-25253
- CVE-2026-25253: One-Click RCE in OpenClaw via Auth Token Theft (github_poc): https://github.com/KajzingerAkos/CVE-2026-25253

## 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-25253 and fix it if it is affected.

What it is: CVE-2026-25253 is a high-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 1 Feb 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25253 exists.

Affected packages and fixed versions:
- clawdbot (npm): affected all versions; fixed in 2026.1.29
- clawdbot (npm): affected all versions; fixed in 2026.1.29

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

## Sources

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

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