<?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-06T11:56:48.340841+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-32982</id>
    <title>BREW-openclaw-cli-CVE-2026-32982 — OpenClaw Telegram media fetch errors exposed bot tokens in logged file URLs</title>
    <updated>2026-10-06T11:56:48.343879+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary
`openclaw` versions `&lt;= 2026.3.12` could include raw Telegram bot tokens in media fetch error strings when inbound Telegram media downloads failed.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (`npm`)
- Affected versions: `&lt;= 2026.3.12`
- Fixed version: `2026.3.13`</p>
<p>### 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&lt;TOKEN&gt;/...`, so the resulting error strings could leak bot tokens into logs, console output, or any downstream error surface that rendered the exception text.</p>
<p>This issue is in scope under OpenClaw's trust model because the leaked secret is an OpenClaw-operated integration credential, not a user-supplied third-party secret.</p>
<p>### 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.</p>
<p>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`).</p>
<p>### Fix Commit(s)
- `7a53eb7ea8295b08be137e231c9a98c1a79b5cd5`</p>
<p>Thanks @space08 for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32982"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329485</id>
    <title>EUVD-2026-329485</title>
    <updated>2026-10-06T11:56:48.343940+00:00</updated>
    <content>EUVD-2026-329485</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329485"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32982</id>
    <title>fkie_cve-2026-32982</title>
    <updated>2026-10-06T11:56:48.343957+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32982"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xqg6-p6hx-f752</id>
    <title>GHSA-xqg6-p6hx-f752</title>
    <updated>2026-10-06T11:56:48.343980+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xqg6-p6hx-f752"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0743</id>
    <title>WID-SEC-W-2026-0743 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-06T11:56:48.343995+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um seine Privilegien zu erhöhen und um vertrauliche Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0743"/>
  </entry>
</feed>
