# CVE-2026-100577: OpenClaw before 2026.8.1 Server-Side Request Forgery via Video Asset

> A malicious provider can return private URLs, causing the OpenClaw CLI to make requests to internal services, enabling access to internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA: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:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-3qmc-rwv9-q36h, GHSA-fvxr-9g24-x3hf, MINI-f79p-v9gm-74pv

## What is CVE-2026-100577?

CVE-2026-100577 is a medium-severity server-side request forgery vulnerability in OpenClaw, published on 26 Sep 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 versions before 2026.8.1 fail to validate video asset URLs returned by providers, allowing server-side requests to private destinations. A malicious or compromised provider can return private or loopback URLs to cause the CLI to make requests to internal services accessible from the OpenClaw host.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-100577 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100577 is a medium-severity server-side request forgery vulnerability in OpenClaw, published on 26 Sep 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-100577 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-100577/ (Markdown: https://insights.sbomify.com/CVE-2026-100577/index.md)
```

## Sources

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

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