# CVE-2026-6011: OpenClaw assertPublicHostname web-fetch.ts server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in OpenClaw's web-fetch tool to access internal resources.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-52vj-fvrv-7q82

## What is CVE-2026-6011?

CVE-2026-6011 is a medium-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in OpenClaw up to 2026.1.26. Affected by this issue is some unknown functionality of the file src/agents/tools/web-fetch.ts of the component assertPublicHostname Handler. Executing a manipulation can lead to server-side request forgery. The attack can be executed remotely. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been made available to the public and could be used for attacks. Upgrading to version 2026.1.29 can resolve this issue. This patch is called b623557a2ec7e271bda003eb3ac33fbb2e218505. Upgrading the affected component is advised.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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


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

Products: Openclaw Openclaw.

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

Upgrade openclaw to 2026.1.29 or later.

## Is CVE-2026-6011 being exploited?

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

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

What it is: CVE-2026-6011 is a medium-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6011 exists.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.1.29
- openclaw (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-6011/ (Markdown: https://insights.sbomify.com/CVE-2026-6011/index.md)
```

## Sources

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

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