Internal resource disclosure via unguarded media fetches
Published Mar 5, 2026 · Updated Mar 5, 2026
SSRF in OpenClaw before 2026.2.2 allows remote attackers to read internal HTTP(S) resources through crafted attachment media URLs. The attachment and media hydration paths passed attacker-influenced URLs to raw fetch operations without private-address, DNS-pinning, or redirect checks. Exploitation requires control of a media URL through sendAttachment or an auto-reply path and returns reachable internal response bytes as an outbound attachment, without granting code execution.
Summary
What happened
SSRF in OpenClaw before 2026.2.2 allows remote attackers to read internal HTTP(S) resources through crafted attachment media URLs. The attachment and media hydration paths passed attacker-influenced URLs to raw fetch operations without private-address, DNS-pinning, or redirect checks. Exploitation requires control of a media URL through sendAttachment or an auto-reply path and returns reachable internal response bytes as an outbound attachment, without granting code execution.
The record
- CVE
- CVE-2026-28467
- Published
- Mar 5, 2026
- Updated
- Mar 5, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 5, 2026CVE publishedPublication date reported by the CVE source.
- Mar 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.2.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream attachment media URL SSRF proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo