<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T22:43:31.795692+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-27003</id>
    <title>BREW-openclaw-cli-CVE-2026-27003 — OpenClaw: Telegram bot token exposure via logs</title>
    <updated>2026-09-30T22:43:31.840508+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Vulnerability</p>
<p>Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include `https://api.telegram.org/bot&lt;token&gt;/...`). OpenClaw previously logged these strings without redaction, which could leak the bot token into logs, crash reports, CI output, or support bundles.</p>
<p>## Impact</p>
<p>Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Affected: `&lt;= 2026.2.14`
- Fixed: `&gt;= 2026.2.15` (next release)</p>
<p>## Mitigation</p>
<p>- Upgrade to `openclaw &gt;= 2026.2.15` when released.
- Rotate the Telegram bot token if it may have been exposed.</p>
<p>## Fix Commit(s)</p>
<p>- cf6990701b258bb9cc4ac7f6c7bdf05016e7f6e46</p>
<p>Thanks @aether-ai-agent for reporting.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/brew-openclaw-cli-cve-2026-27003"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-27003</id>
    <title>CVE-2026-27003 — OpenClaw: Telegram bot token exposure via logs</title>
    <updated>2026-09-30T22:43:31.840628+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openclaw</p>
<p>OpenClaw is a personal AI assistant. Telegram bot tokens can appear in error messages and stack traces (for example, when request URLs include `https://api.telegram.org/bot&lt;token&gt;/...`). Prior to version 2026.2.15, OpenClaw logged these strings without redaction, which could leak the bot token into logs, crash reports, CI output, or support bundles. Disclosure of a Telegram bot token allows an attacker to impersonate the bot and take over Bot API access. Users should upgrade to version 2026.2.15 to obtain a fix and rotate the Telegram bot token if it may have been exposed.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-27003"/>
  </entry>
</feed>
