<?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://cve.radiocsirt.org</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>Tue, 06 Oct 2026 06:55:32 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-32982 — OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32982</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary
`openclaw` versions `&amp;lt;= 2026.3.12` could include raw Telegram bot tokens in media fetch error strings when inbound Telegram media downloads failed.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (`npm`)
- Affected versions: `&amp;lt;= 2026.3.12`
- Fixed version: `2026.3.13`&lt;/p&gt;
&lt;p&gt;### Details
The vulnerable path was `fetchRemoteMedia()` in `src/media/fetch.ts`. In affected releases, fetch and HTTP error paths embedded the original Telegram file URL into `MediaFetchError` messages. For Telegram media, those URLs can include `/file/bot&amp;lt;TOKEN&amp;gt;/...`, so the resulting error strings could leak bot tokens into logs, console output, or any downstream error surface that rendered the exception text.&lt;/p&gt;
&lt;p&gt;This issue is in scope under OpenClaw&amp;#39;s trust model because the leaked secret is an OpenClaw-operated integration credential, not a user-supplied third-party secret.&lt;/p&gt;
&lt;p&gt;### Fix
`openclaw@2026.3.13` redacts sensitive media URLs before constructing fetch error messages. Current code routes the source URL and follow-on error paths through `redactMediaUrl()` / `redactSensitiveText()`, so Telegram bot tokens are no longer emitted in those error strings.&lt;/p&gt;
&lt;p&gt;Regression coverage exists in `src/media/fetch.test.ts` (`redacts Telegram bot tokens from fetch failure messages` and `redacts Telegram bot tokens from HTTP error messages`).&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `7a53eb7ea8295b08be137e231c9a98c1a79b5cd5`&lt;/p&gt;
&lt;p&gt;Thanks @space08 for reporting.&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
`openclaw` versions `&amp;lt;= 2026.3.12` could include raw Telegram bot tokens in media fetch error strings when inbound Telegram media downloads failed.&lt;/p&gt;
&lt;p&gt;### Affected Packages / Versions
- Package: `openclaw` (`npm`)
- Affected versions: `&amp;lt;= 2026.3.12`
- Fixed version: `2026.3.13`&lt;/p&gt;
&lt;p&gt;### Details
The vulnerable path was `fetchRemoteMedia()` in `src/media/fetch.ts`. In affected releases, fetch and HTTP error paths embedded the original Telegram file URL into `MediaFetchError` messages. For Telegram media, those URLs can include `/file/bot&amp;lt;TOKEN&amp;gt;/...`, so the resulting error strings could leak bot tokens into logs, console output, or any downstream error surface that rendered the exception text.&lt;/p&gt;
&lt;p&gt;This issue is in scope under OpenClaw&amp;#39;s trust model because the leaked secret is an OpenClaw-operated integration credential, not a user-supplied third-party secret.&lt;/p&gt;
&lt;p&gt;### Fix
`openclaw@2026.3.13` redacts sensitive media URLs before constructing fetch error messages. Current code routes the source URL and follow-on error paths through `redactMediaUrl()` / `redactSensitiveText()`, so Telegram bot tokens are no longer emitted in those error strings.&lt;/p&gt;
&lt;p&gt;Regression coverage exists in `src/media/fetch.test.ts` (`redacts Telegram bot tokens from fetch failure messages` and `redacts Telegram bot tokens from HTTP error messages`).&lt;/p&gt;
&lt;p&gt;### Fix Commit(s)
- `7a53eb7ea8295b08be137e231c9a98c1a79b5cd5`&lt;/p&gt;
&lt;p&gt;Thanks @space08 for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32982</guid>
    </item>
    <item>
      <title>EUVD-2026-329485</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329485</link>
      <description>EUVD-2026-329485</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329485</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32982</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32982</link>
      <description>&lt;p&gt;OpenClaw before 2026.3.13 contains an information disclosure vulnerability in the fetchRemoteMedia function that exposes Telegram bot tokens in error messages. When media downloads fail, the original Telegram file URLs containing bot tokens are embedded in MediaFetchError strings and leaked to logs and error surfaces.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw before 2026.3.13 contains an information disclosure vulnerability in the fetchRemoteMedia function that exposes Telegram bot tokens in error messages. When media downloads fail, the original Telegram file URLs containing bot tokens are embedded in MediaFetchError strings and leaked to logs and error surfaces.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32982</guid>
    </item>
    <item>
      <title>GHSA-xqg6-p6hx-f752</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-xqg6-p6hx-f752</link>
      <description>&lt;p&gt;OpenClaw before 2026.3.13 contains an information disclosure vulnerability in the fetchRemoteMedia function that exposes Telegram bot tokens in error messages. When media downloads fail, the original Telegram file URLs containing bot tokens are embedded in MediaFetchError strings and leaked to logs and error surfaces.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw before 2026.3.13 contains an information disclosure vulnerability in the fetchRemoteMedia function that exposes Telegram bot tokens in error messages. When media downloads fail, the original Telegram file URLs containing bot tokens are embedded in MediaFetchError strings and leaked to logs and error surfaces.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-xqg6-p6hx-f752</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0743 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0743</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um seine Privilegien zu erhöhen und um vertrauliche Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um seine Privilegien zu erhöhen und um vertrauliche Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0743</guid>
    </item>
  </channel>
</rss>
