CVE-2026-28467
Received Received - Intake
SSRF Vulnerability in OpenClaw Attachment URL Handling

Publication date: 2026-03-05

Last updated on: 2026-03-09

Assigner: VulnCheck

Description
OpenClaw versions prior to 2026.2.2 contain a server-side request forgery vulnerability in attachment and media URL hydration that allows remote attackers to fetch arbitrary HTTP(S) URLs. Attackers who can influence media URLs through model-controlled sendAttachment or auto-reply mechanisms can trigger SSRF to internal resources and exfiltrate fetched response bytes as outbound attachments.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-05
Last Modified
2026-03-09
Generated
2026-05-07
AI Q&A
2026-03-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
openclaw openclaw to 2026.2.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in OpenClaw versions prior to 2026.2.2 and is a server-side request forgery (SSRF) issue. It occurs in the attachment and media URL hydration process, allowing remote attackers to make the server fetch arbitrary HTTP or HTTPS URLs.

Attackers who can influence media URLs through features like model-controlled sendAttachment or auto-reply mechanisms can exploit this vulnerability to trigger SSRF. This means they can cause the server to access internal resources and potentially exfiltrate data by embedding the fetched response bytes as outbound attachments.


How can this vulnerability impact me? :

The impact of this vulnerability includes unauthorized access to internal resources that are normally not accessible from outside the network. Attackers can leverage this to gather sensitive information or perform further attacks within the internal network.

Additionally, attackers can exfiltrate data by embedding the fetched response bytes as outbound attachments, potentially leading to data leakage.

The vulnerability has a CVSS v3.1 base score of 5.3, indicating a medium severity, and a CVSS v4.0 base score of 6.9, indicating a higher risk due to its potential impact on integrity and availability.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart