<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 05:48:32 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-28467 — OpenClaw affected by SSRF via attachment/media URL hydration</title>
      <link>https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28467</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Versions of the `openclaw` npm package prior to `2026.2.2` could be coerced into fetching arbitrary `http(s)` URLs during attachment/media hydration. An attacker who can influence the media URL (for example via model-controlled `sendAttachment` or auto-reply media URLs) could trigger SSRF to internal resources and exfiltrate the fetched bytes as an outbound attachment.&lt;/p&gt;
&lt;p&gt;### Plain-English Explanation&lt;/p&gt;
&lt;p&gt;OpenClaw can send files by downloading them first.&lt;/p&gt;
&lt;p&gt;On vulnerable versions (`&amp;lt; 2026.2.2`), if an attacker could get OpenClaw to treat a URL as the “file to attach”, OpenClaw would download that URL from the gateway machine and then send the downloaded bytes back out as an attachment.&lt;/p&gt;
&lt;p&gt;That matters because the gateway can often reach internal-only endpoints that an attacker cannot (for example `127.0.0.1` services, private RFC1918 addresses, or cloud metadata endpoints). This is a data-leak risk.&lt;/p&gt;
&lt;p&gt;This does not directly grant code execution or shell access; it is about making the gateway perform HTTP requests and returning the response bytes.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Affected: `&amp;lt; 2026.2.2`
- Fixed: `&amp;gt;= 2026.2.2`&lt;/p&gt;
&lt;p&gt;Release timeline (npm):&lt;/p&gt;
&lt;p&gt;- `2026.2.1` published `2026-02-02T11:45:27Z`
- `2026.2.2` published `2026-02-04T00:56:41Z`
- This advisory was created `2026-02-05T10:42:26Z`&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In affected versions, remote media fetching performed a raw `fetch(url)` without SSRF protections.&lt;/p&gt;
&lt;p&gt;Starting in `2026.2.2`, remote media f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Versions of the `openclaw` npm package prior to `2026.2.2` could be coerced into fetching arbitrary `http(s)` URLs during attachment/media hydration. An attacker who can influence the media URL (for example via model-controlled `sendAttachment` or auto-reply media URLs) could trigger SSRF to internal resources and exfiltrate the fetched bytes as an outbound attachment.&lt;/p&gt;
&lt;p&gt;### Plain-English Explanation&lt;/p&gt;
&lt;p&gt;OpenClaw can send files by downloading them first.&lt;/p&gt;
&lt;p&gt;On vulnerable versions (`&amp;lt; 2026.2.2`), if an attacker could get OpenClaw to treat a URL as the “file to attach”, OpenClaw would download that URL from the gateway machine and then send the downloaded bytes back out as an attachment.&lt;/p&gt;
&lt;p&gt;That matters because the gateway can often reach internal-only endpoints that an attacker cannot (for example `127.0.0.1` services, private RFC1918 addresses, or cloud metadata endpoints). This is a data-leak risk.&lt;/p&gt;
&lt;p&gt;This does not directly grant code execution or shell access; it is about making the gateway perform HTTP requests and returning the response bytes.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions&lt;/p&gt;
&lt;p&gt;- Package: `openclaw` (npm)
- Affected: `&amp;lt; 2026.2.2`
- Fixed: `&amp;gt;= 2026.2.2`&lt;/p&gt;
&lt;p&gt;Release timeline (npm):&lt;/p&gt;
&lt;p&gt;- `2026.2.1` published `2026-02-02T11:45:27Z`
- `2026.2.2` published `2026-02-04T00:56:41Z`
- This advisory was created `2026-02-05T10:42:26Z`&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;In affected versions, remote media fetching performed a raw `fetch(url)` without SSRF protections.&lt;/p&gt;
&lt;p&gt;Starting in `2026.2.2`, remote media f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/brew-openclaw-cli-cve-2026-28467</guid>
    </item>
    <item>
      <title>CVE-2026-28467 — OpenClaw &lt; 2026.2.2 - SSRF via Attachment Media URL Hydration</title>
      <link>https://db.gcve.eu/vuln/cve-2026-28467</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenClaw&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-28467</guid>
    </item>
  </channel>
</rss>
