<?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-03T05:24:22.154403+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/cve-2026-32905</id>
    <title>CVE-2026-32905 — OpenClaw &lt; 2026.5.4 - Unauthorized Device-Pairing Bootstrap Code Issuance via Chat Command</title>
    <updated>2026-10-03T05:24:22.155947+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenClaw</p>
<p>OpenClaw before 2026.5.4 contains an authorization bypass vulnerability in the bundled device-pair plugin that allows non-owner authorized chat senders to issue device-pairing bootstrap codes without proper scope validation. Attackers with chat command access can create setup codes to enroll devices with operator/node capabilities, granting persistent credentials until manual removal.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-32905"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-xr4f-mjxj-w6w5</id>
    <title>GHSA-xr4f-mjxj-w6w5 — OpenClaw: Non-owner chat senders could issue device-pairing bootstrap codes</title>
    <updated>2026-10-03T05:24:22.155996+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>The bundled device-pair plugin exposed `/pair` on normal chat command surfaces. In affected releases, authorized non-owner chat senders could issue device-pairing bootstrap codes without having owner, admin, or pairing scope.</p>
<p>This issue does not affect unauthenticated users. The caller must already be allowed to send commands to the agent through a configured chat channel.</p>
<p>### Affected configurations</p>
<p>This affects deployments where the bundled device-pair plugin is enabled and a non-owner sender is authorized to use normal chat commands, such as in a configured Telegram, Discord, or Slack agent.</p>
<p>### Impact</p>
<p>A non-owner authorized sender could create a setup code and use it before expiry to enroll a device with operator/node capabilities. That device would then retain persistent credentials until removed.</p>
<p>### Patched Versions</p>
<p>The first stable patched version is `2026.5.4`.</p>
<p>### Mitigations</p>
<p>Upgrade to `openclaw@2026.5.4` or later. Review paired devices and remove any unexpected entries. In shared chat channels, keep command access limited to users who should be allowed to manage device pairing.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-xr4f-mjxj-w6w5"/>
  </entry>
</feed>
