# GHSA-56f2-hvwg-5743: OpenClaw affected by SSRF in Image Tool Remote Fetch

> Attackers can force OpenClaw to make unauthorized HTTP requests to internal network targets via the Image tool, potentially exposing internal data.

- **Severity:** Not scored
- **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 Feb 2026

## What is GHSA-56f2-hvwg-5743?

GHSA-56f2-hvwg-5743 is a server-side request forgery vulnerability in openclaw, published on 17 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

## Summary

A server-side request forgery (SSRF) vulnerability in the Image tool allowed attackers to force OpenClaw to make HTTP requests to arbitrary internal or restricted network targets.

## Affected Versions

- npm: openclaw <= 2026.2.1

## Patched Versions

- npm: openclaw 2026.2.2 and later

## Fix Commits

- 81c68f582d4a9a20d9cca9f367d2da9edc5a65ae (guard remote media fetches with SSRF checks)
- 9bd64c8a1f91dda602afc1d5246a2ff2be164647 (expand SSRF guard coverage)

## Details

The Image tool accepts file paths, file:// URLs, data: URLs, and http(s) URLs. In vulnerable versions, http(s) URLs were fetched without SSRF protections, enabling requests to localhost, RFC1918, link-local, and cloud metadata targets.

This was fixed by routing remote media fetching through the SSRF guard (private/internal IP + hostname blocking, redirect hardening, DNS pinning).

## Exploitability Notes

- Requires attacker-controlled invocation of the Image tool (direct tool access, or a gateway/channel surface that forwards untrusted `image` arguments into tool calls).
- The image tool expects the fetched content to be an image. Many high-value SSRF targets return text/JSON (for example cloud metadata endpoints), which will typically fail media-type validation. In practice, the most direct confidentiality impact comes from internal endpoints that actually return images (screenshots/renderers, camera snapshots, chart exports, etc.).
- Remote fetches are GET-only with no custom headers. Some metadata services require special headers or session tokens (for example GCP `Metadata-Flavor`, AWS IMDSv2 token), which can further reduce the likelihood of direct credential theft in some environments.
- Despite the above constraints, SSRF remains a powerful primitive: it can enable internal network probing and access to unauthenticated/internal HTTP endpoints, and can chain with other weaknesses if present.

Thanks @p80n-sec for reporting.

## Which versions are affected by GHSA-56f2-hvwg-5743?

2 open source packages ship an affected version, including openclaw.


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

## How do I fix GHSA-56f2-hvwg-5743?

Upgrade openclaw to 2026.2.2 or later.

## Is GHSA-56f2-hvwg-5743 being exploited?

There is no known exploitation of GHSA-56f2-hvwg-5743 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-56f2-hvwg-5743 and fix it if it is affected.

What it is: GHSA-56f2-hvwg-5743 is a server-side request forgery vulnerability in openclaw, published on 17 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-56f2-hvwg-5743 in the wild and no public exploit code.

Affected packages and fixed versions:
- openclaw (npm): affected all versions; fixed in 2026.2.2
- openclaw (npm): affected all versions; fixed in 2026.2.2

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/GHSA-56f2-hvwg-5743/ (Markdown: https://insights.sbomify.com/GHSA-56f2-hvwg-5743/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-56f2-hvwg-5743

---
From sbomify Insights: https://insights.sbomify.com/GHSA-56f2-hvwg-5743/
Summaries are generated and may contain mistakes; the official description above is the record.