<?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>Tue, 06 Oct 2026 06:11:58 +0000</lastBuildDate>
    <item>
      <title>BREW-openclaw-cli-CVE-2026-32027 — OpenClaw DM pairing-store identities could satisfy group allowlist authorization</title>
      <link>https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32027</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: openclaw-cli&lt;/p&gt;
&lt;p&gt;## Summary
DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.&lt;/p&gt;
&lt;p&gt;## Details
In affected versions, group allowlist evaluation could inherit identities from the DM pairing store. A sender approved via DM pairing could satisfy group sender allowlist checks without being explicitly present in `groupAllowFrom`.&lt;/p&gt;
&lt;p&gt;This is an authorization-policy boundary issue between DM pairing and group allowlists.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- `openclaw` (npm): affected `&amp;lt;= 2026.2.25` (latest published npm version at triage time)
- `openclaw` (npm): patched `&amp;gt;= 2026.2.26` (planned next release)&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- `openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0`
- `openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9`&lt;/p&gt;
&lt;p&gt;## Release Process Note
`patched_versions` is pre-set to the planned next release (`2026.2.26`) so once npm release is published, maintainers can publish the advisory without additional metadata edits.&lt;/p&gt;
&lt;p&gt;## Maintainer Timeline Note
Maintainers landed the initial fix before this report was filed; this report still provided useful independent confirmation of the issue class and exploit path.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&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
DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.&lt;/p&gt;
&lt;p&gt;## Details
In affected versions, group allowlist evaluation could inherit identities from the DM pairing store. A sender approved via DM pairing could satisfy group sender allowlist checks without being explicitly present in `groupAllowFrom`.&lt;/p&gt;
&lt;p&gt;This is an authorization-policy boundary issue between DM pairing and group allowlists.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- `openclaw` (npm): affected `&amp;lt;= 2026.2.25` (latest published npm version at triage time)
- `openclaw` (npm): patched `&amp;gt;= 2026.2.26` (planned next release)&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- `openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0`
- `openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9`&lt;/p&gt;
&lt;p&gt;## Release Process Note
`patched_versions` is pre-set to the planned next release (`2026.2.26`) so once npm release is published, maintainers can publish the advisory without additional metadata edits.&lt;/p&gt;
&lt;p&gt;## Maintainer Timeline Note
Maintainers landed the initial fix before this report was filed; this report still provided useful independent confirmation of the issue class and exploit path.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32027</guid>
    </item>
    <item>
      <title>cnvd-2026-14856</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2026-14856</link>
      <description>cnvd-2026-14856</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2026-14856</guid>
    </item>
    <item>
      <title>EUVD-2026-329423</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329423</link>
      <description>EUVD-2026-329423</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329423</guid>
    </item>
    <item>
      <title>fkie_cve-2026-32027</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32027</link>
      <description>&lt;p&gt;OpenClaw versions prior to 2026.2.26 contain an authorization bypass vulnerability where DM pairing-store identities are incorrectly eligible for group allowlist authorization checks. Attackers can exploit this cross-context authorization flaw by using a sender approved via DM pairing to satisfy group sender allowlist checks without explicit presence in groupAllowFrom, bypassing group message access controls.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;OpenClaw versions prior to 2026.2.26 contain an authorization bypass vulnerability where DM pairing-store identities are incorrectly eligible for group allowlist authorization checks. Attackers can exploit this cross-context authorization flaw by using a sender approved via DM pairing to satisfy group sender allowlist checks without explicit presence in groupAllowFrom, bypassing group message access controls.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-32027</guid>
    </item>
    <item>
      <title>GHSA-jv6r-27ww-4gw4 — OpenClaw DM pairing-store identities could satisfy group allowlist authorization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-jv6r-27ww-4gw4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: openclaw&lt;/p&gt;
&lt;p&gt;## Summary
DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.&lt;/p&gt;
&lt;p&gt;## Details
In affected versions, group allowlist evaluation could inherit identities from the DM pairing store. A sender approved via DM pairing could satisfy group sender allowlist checks without being explicitly present in `groupAllowFrom`.&lt;/p&gt;
&lt;p&gt;This is an authorization-policy boundary issue between DM pairing and group allowlists.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- `openclaw` (npm): affected `&amp;lt;= 2026.2.25` (latest published npm version at triage time)
- `openclaw` (npm): patched `&amp;gt;= 2026.2.26` (planned next release)&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- `openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0`
- `openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9`&lt;/p&gt;
&lt;p&gt;## Release Process Note
`patched_versions` is pre-set to the planned next release (`2026.2.26`) so once npm release is published, maintainers can publish the advisory without additional metadata edits.&lt;/p&gt;
&lt;p&gt;## Maintainer Timeline Note
Maintainers landed the initial fix before this report was filed; this report still provided useful independent confirmation of the issue class and exploit path.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&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
DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.&lt;/p&gt;
&lt;p&gt;## Details
In affected versions, group allowlist evaluation could inherit identities from the DM pairing store. A sender approved via DM pairing could satisfy group sender allowlist checks without being explicitly present in `groupAllowFrom`.&lt;/p&gt;
&lt;p&gt;This is an authorization-policy boundary issue between DM pairing and group allowlists.&lt;/p&gt;
&lt;p&gt;## Affected Packages / Versions
- `openclaw` (npm): affected `&amp;lt;= 2026.2.25` (latest published npm version at triage time)
- `openclaw` (npm): patched `&amp;gt;= 2026.2.26` (planned next release)&lt;/p&gt;
&lt;p&gt;## Fix Commit(s)
- `openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0`
- `openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9`&lt;/p&gt;
&lt;p&gt;## Release Process Note
`patched_versions` is pre-set to the planned next release (`2026.2.26`) so once npm release is published, maintainers can publish the advisory without additional metadata edits.&lt;/p&gt;
&lt;p&gt;## Maintainer Timeline Note
Maintainers landed the initial fix before this report was filed; this report still provided useful independent confirmation of the issue class and exploit path.&lt;/p&gt;
&lt;p&gt;OpenClaw thanks @tdjackey for reporting.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-jv6r-27ww-4gw4</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-0586 — OpenClaw: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0586</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Code auszuführen, sich erhöhte Berechtigungen zu verschaffen, Daten zu manipulieren, einen Denial-of-Service-Zustand herbeizuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in OpenClaw ausnutzen, um beliebigen Code auszuführen, sich erhöhte Berechtigungen zu verschaffen, Daten zu manipulieren, einen Denial-of-Service-Zustand herbeizuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen oder andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0586</guid>
    </item>
  </channel>
</rss>
