<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T08:22:28.033607+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-53840</id>
    <title>BREW-openclaw-cli-CVE-2026-53840 — OpenClaw: MCP Streamable HTTP redirects could forward configured custom headers to another origin</title>
    <updated>2026-10-04T08:22:28.065889+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary</p>
<p>OpenClaw supports remote MCP Streamable HTTP servers with operator-configured custom headers. In affected releases, those headers could be forwarded when the MCP endpoint responded with a cross-origin redirect.</p>
<p>This issue is limited to configured MCP Streamable HTTP servers that use custom headers. It does not expose unrelated OpenClaw credentials.</p>
<p>### Affected configurations</p>
<p>This affects deployments where an MCP server is configured with:</p>
<p>- `transportType: "streamable-http"`
- sensitive custom headers under `mcp.servers.*.headers`
- an MCP endpoint that is malicious, compromised, or able to redirect to another origin</p>
<p>### Impact</p>
<p>Custom MCP headers, such as API keys or tenant-routing headers, could be sent to the redirect target. The exposed credential scope depends on the header the operator configured for that MCP server.</p>
<p>### Patched Versions</p>
<p>The first stable patched version is `2026.5.12`.</p>
<p>### Mitigations</p>
<p>Upgrade to `openclaw@2026.5.8` or later. Before upgrading, avoid custom MCP headers with servers you do not fully trust, and rotate any MCP-specific credentials that may have been exposed by a redirecting endpoint.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-53840"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-327790</id>
    <title>EUVD-2026-327790</title>
    <updated>2026-10-04T08:22:28.065953+00:00</updated>
    <content>EUVD-2026-327790</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-327790"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53840</id>
    <title>fkie_cve-2026-53840</title>
    <updated>2026-10-04T08:22:28.065970+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>OpenClaw before 2026.5.12 contains an information disclosure vulnerability in streamable-http MCP servers that forwards operator-configured custom headers during cross-origin redirects. Attackers controlling or compromising an MCP endpoint can redirect requests to exfiltrate sensitive headers like API keys or tenant-routing credentials to attacker-controlled origins.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-53840"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rjxq-qqhf-8hwh</id>
    <title>GHSA-rjxq-qqhf-8hwh — OpenClaw: MCP Streamable HTTP redirects could forward configured custom headers to another origin</title>
    <updated>2026-10-04T08:22:28.065993+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary</p>
<p>OpenClaw supports remote MCP Streamable HTTP servers with operator-configured custom headers. In affected releases, those headers could be forwarded when the MCP endpoint responded with a cross-origin redirect.</p>
<p>This issue is limited to configured MCP Streamable HTTP servers that use custom headers. It does not expose unrelated OpenClaw credentials.</p>
<p>### Affected configurations</p>
<p>This affects deployments where an MCP server is configured with:</p>
<p>- `transportType: "streamable-http"`
- sensitive custom headers under `mcp.servers.*.headers`
- an MCP endpoint that is malicious, compromised, or able to redirect to another origin</p>
<p>### Impact</p>
<p>Custom MCP headers, such as API keys or tenant-routing headers, could be sent to the redirect target. The exposed credential scope depends on the header the operator configured for that MCP server.</p>
<p>### Patched Versions</p>
<p>The first stable patched version is `2026.5.12`.</p>
<p>### Mitigations</p>
<p>Upgrade to `openclaw@2026.5.8` or later. Before upgrading, avoid custom MCP headers with servers you do not fully trust, and rotate any MCP-specific credentials that may have been exposed by a redirecting endpoint.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-rjxq-qqhf-8hwh"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1738</id>
    <title>WID-SEC-W-2026-1738 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-04T08:22:28.066026+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Sicherheitsmechanismen zu umgehen, erhöhte Berechtigungen zu erlangen, Informationen offenzulegen, Konfigurationen zu manipulieren, beliebige Befehle oder Code auszuführen sowie interne Systeme über SSRF anzugreifen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1738"/>
  </entry>
</feed>
