<?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>Sun, 04 Oct 2026 04:11:08 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-53817 — OpenClaw: Control UI locality spoofing could mint a durable admin device token</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-53817</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In affected LAN/shared-token Control UI deployments, a caller could spoof locality information used during Control UI pairing and obtain a durable admin-capable device token.&lt;/p&gt;
&lt;p&gt;This issue is limited to deployments where the caller already has the network/authentication foothold needed to reach the Control UI pairing path. It is not an unauthenticated internet exposure issue.&lt;/p&gt;
&lt;p&gt;### Affected configurations&lt;/p&gt;
&lt;p&gt;This affects configurations such as LAN-bound gateways or shared-token Control UI access where locality signals were accepted as sufficient for pairing decisions.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A temporary or shared Control UI access path could be turned into a persistent admin device token. That token could remain useful after the shared gateway token was rotated, unless the paired device was removed.&lt;/p&gt;
&lt;p&gt;The issue is a pairing/locality validation problem: locality-derived trust was stronger than it should have been.&lt;/p&gt;
&lt;p&gt;### Patched Versions&lt;/p&gt;
&lt;p&gt;The first stable patched version is `2026.5.22`.&lt;/p&gt;
&lt;p&gt;### Mitigations&lt;/p&gt;
&lt;p&gt;Upgrade to `openclaw@2026.5.22` or later. For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.&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&lt;/p&gt;
&lt;p&gt;In affected LAN/shared-token Control UI deployments, a caller could spoof locality information used during Control UI pairing and obtain a durable admin-capable device token.&lt;/p&gt;
&lt;p&gt;This issue is limited to deployments where the caller already has the network/authentication foothold needed to reach the Control UI pairing path. It is not an unauthenticated internet exposure issue.&lt;/p&gt;
&lt;p&gt;### Affected configurations&lt;/p&gt;
&lt;p&gt;This affects configurations such as LAN-bound gateways or shared-token Control UI access where locality signals were accepted as sufficient for pairing decisions.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A temporary or shared Control UI access path could be turned into a persistent admin device token. That token could remain useful after the shared gateway token was rotated, unless the paired device was removed.&lt;/p&gt;
&lt;p&gt;The issue is a pairing/locality validation problem: locality-derived trust was stronger than it should have been.&lt;/p&gt;
&lt;p&gt;### Patched Versions&lt;/p&gt;
&lt;p&gt;The first stable patched version is `2026.5.22`.&lt;/p&gt;
&lt;p&gt;### Mitigations&lt;/p&gt;
&lt;p&gt;Upgrade to `openclaw@2026.5.22` or later. For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-53817</guid>
    </item>
    <item>
      <title>EUVD-2026-329569</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329569</link>
      <description>EUVD-2026-329569</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329569</guid>
    </item>
    <item>
      <title>fkie_cve-2026-53817</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-53817</link>
      <description>&lt;p&gt;OpenClaw before 2026.5.22 contains a locality validation vulnerability in Control UI pairing that allows attackers with network access to spoof locality information and obtain durable admin-capable device tokens. Attackers can exploit insufficient locality-derived trust validation to convert temporary shared access into persistent administrative credentials that survive token rotation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw before 2026.5.22 contains a locality validation vulnerability in Control UI pairing that allows attackers with network access to spoof locality information and obtain durable admin-capable device tokens. Attackers can exploit insufficient locality-derived trust validation to convert temporary shared access into persistent administrative credentials that survive token rotation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-53817</guid>
    </item>
    <item>
      <title>GHSA-chr9-m4q2-76hw — OpenClaw: Control UI locality spoofing could mint a durable admin device token</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-chr9-m4q2-76hw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In affected LAN/shared-token Control UI deployments, a caller could spoof locality information used during Control UI pairing and obtain a durable admin-capable device token.&lt;/p&gt;
&lt;p&gt;This issue is limited to deployments where the caller already has the network/authentication foothold needed to reach the Control UI pairing path. It is not an unauthenticated internet exposure issue.&lt;/p&gt;
&lt;p&gt;### Affected configurations&lt;/p&gt;
&lt;p&gt;This affects configurations such as LAN-bound gateways or shared-token Control UI access where locality signals were accepted as sufficient for pairing decisions.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A temporary or shared Control UI access path could be turned into a persistent admin device token. That token could remain useful after the shared gateway token was rotated, unless the paired device was removed.&lt;/p&gt;
&lt;p&gt;The issue is a pairing/locality validation problem: locality-derived trust was stronger than it should have been.&lt;/p&gt;
&lt;p&gt;### Patched Versions&lt;/p&gt;
&lt;p&gt;The first stable patched version is `2026.5.22`.&lt;/p&gt;
&lt;p&gt;### Mitigations&lt;/p&gt;
&lt;p&gt;Upgrade to `openclaw@2026.5.22` or later. For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In affected LAN/shared-token Control UI deployments, a caller could spoof locality information used during Control UI pairing and obtain a durable admin-capable device token.&lt;/p&gt;
&lt;p&gt;This issue is limited to deployments where the caller already has the network/authentication foothold needed to reach the Control UI pairing path. It is not an unauthenticated internet exposure issue.&lt;/p&gt;
&lt;p&gt;### Affected configurations&lt;/p&gt;
&lt;p&gt;This affects configurations such as LAN-bound gateways or shared-token Control UI access where locality signals were accepted as sufficient for pairing decisions.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A temporary or shared Control UI access path could be turned into a persistent admin device token. That token could remain useful after the shared gateway token was rotated, unless the paired device was removed.&lt;/p&gt;
&lt;p&gt;The issue is a pairing/locality validation problem: locality-derived trust was stronger than it should have been.&lt;/p&gt;
&lt;p&gt;### Patched Versions&lt;/p&gt;
&lt;p&gt;The first stable patched version is `2026.5.22`.&lt;/p&gt;
&lt;p&gt;### Mitigations&lt;/p&gt;
&lt;p&gt;Upgrade to `openclaw@2026.5.22` or later. For older deployments, remove unexpected paired devices and avoid exposing Control UI pairing paths on networks with untrusted clients.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-chr9-m4q2-76hw</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1738 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1738</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Sicherheitsmechanismen zu umgehen, erhöhte Berechtigungen zu erlangen, Informationen offenzulegen, Konfigurationen zu manipulieren, beliebige Befehle oder Code auszuführen sowie interne Systeme über SSRF anzugreifen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um Sicherheitsmechanismen zu umgehen, erhöhte Berechtigungen zu erlangen, Informationen offenzulegen, Konfigurationen zu manipulieren, beliebige Befehle oder Code auszuführen sowie interne Systeme über SSRF anzugreifen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1738</guid>
    </item>
  </channel>
</rss>
