# CVE-2026-62227: OpenClaw 2026.4.14 < 2026.5.26 SSRF via Browser Snapshot

> Attackers can bypass policy checks to access blocked network destinations via unvalidated browser snapshot routes in OpenClaw.

- **Severity:** Medium 4.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-2x93-h3hg-2xfp, GHSA-fc43-vcvc-5qg7, MINI-7576-467j-6x8p

## What is CVE-2026-62227?

CVE-2026-62227 is a medium-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenClaw 2026.4.14 before 2026.5.26 contain a server-side request forgery vulnerability in browser snapshot routes that fail to validate post-navigation destinations. Attackers with lower-trust access can bypass OpenClaw policy checks to reach network destinations that should have been blocked.

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

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

It affects 1 product.


Products: Openclaw Openclaw.

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

Upgrade to a fixed version.

## Is CVE-2026-62227 being exploited?

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

What it is: CVE-2026-62227 is a medium-severity server-side request forgery vulnerability in Openclaw Openclaw, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62227 in the wild and no public exploit code.

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

## Sources

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

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