<?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-20T01:33:08.503133+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-27484</id>
    <title>BREW-openclaw-cli-CVE-2026-27484 — OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows</title>
    <updated>2026-10-20T01:33:08.504805+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Overview</p>
<p>Discord moderation action handling (`timeout`, `kick`, `ban`) used sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context.</p>
<p>## Impact</p>
<p>In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user could request moderation actions by spoofing sender identity fields.</p>
<p>## Affected Packages / Versions</p>
<p>- Package: `openclaw` (npm)
- Latest published affected version (as of 2026-02-19): `2026.2.17`
- Affected range: `&lt;=2026.2.17`
- Fixed in planned next release: `2026.2.18`</p>
<p>## Fix</p>
<p>- Moderation authorization now uses trusted sender context (`requesterSenderId`) instead of untrusted action params.
- Added permission checks for required guild capabilities per action.</p>
<p>## Fix Commit(s)</p>
<p>- `775816035ecc6bb243843f8000c9a58ff609e32d`</p>
<p>Thanks @aether-ai-agent for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-27484"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-27484</id>
    <title>CVE-2026-27484 — OpenClaw Discord moderation authorization used untrusted sender identity in tool-driven flows</title>
    <updated>2026-10-20T01:33:08.504864+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. In versions 2026.2.17 and below, the Discord moderation action handling (timeout, kick, ban) uses sender identity from request parameters in tool-driven flows, instead of trusted runtime sender context. In setups where Discord moderation actions are enabled and the bot has the necessary guild permissions, a non-admin user can request moderation actions by spoofing sender identity fields. This issue has been fixed in version 2026.2.18.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-27484"/>
  </entry>
</feed>
