# CVE-2026-100574: OpenClaw before 2026.8.1 SSRF via Trusted-Host DNS

> An attacker can bypass SSRF protections in OpenClaw by manipulating DNS to resolve trusted hosts to loopback, potentially disclosing internal service data.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-72p2-79fg-pvph, GHSA-97x7-r22f-j42v, MINI-wgpx-8999-xr5g

## What is CVE-2026-100574?

CVE-2026-100574 is a high-severity server-side request forgery vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenClaw (npm package 'openclaw') before 2026.8.1 contains a server-side request forgery vulnerability in its trusted-host DNS checks. For fetches that use the trusted-host DNS recheck, a trusted hostname that resolves to an unspecified address (0.0.0.0 or ::) bypasses the SSRF destination validation. An attacker who can influence DNS for an allowed hostname can therefore cause a guarded fetch to reach a service bound only to loopback and disclose its response; the practical impact depends on the reachable service and the data it returns. Fixed in 2026.8.1.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-100574 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100574 is a high-severity server-side request forgery vulnerability in OpenClaw, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-100574 in the wild and no public exploit code.

Affected product: OpenClaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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