<?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-06T07:07:57.095167+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-32027</id>
    <title>BREW-openclaw-cli-CVE-2026-32027 — OpenClaw DM pairing-store identities could satisfy group allowlist authorization</title>
    <updated>2026-10-06T07:07:57.164511+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>## Summary
DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.</p>
<p>## 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`.</p>
<p>This is an authorization-policy boundary issue between DM pairing and group allowlists.</p>
<p>## Affected Packages / Versions
- `openclaw` (npm): affected `&lt;= 2026.2.25` (latest published npm version at triage time)
- `openclaw` (npm): patched `&gt;= 2026.2.26` (planned next release)</p>
<p>## Fix Commit(s)
- `openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0`
- `openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9`</p>
<p>## 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.</p>
<p>## 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.</p>
<p>OpenClaw thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32027"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-14856</id>
    <title>cnvd-2026-14856</title>
    <updated>2026-10-06T07:07:57.164586+00:00</updated>
    <content>cnvd-2026-14856</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-14856"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329423</id>
    <title>EUVD-2026-329423</title>
    <updated>2026-10-06T07:07:57.164604+00:00</updated>
    <content>EUVD-2026-329423</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329423"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32027</id>
    <title>fkie_cve-2026-32027</title>
    <updated>2026-10-06T07:07:57.164616+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32027"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-jv6r-27ww-4gw4</id>
    <title>GHSA-jv6r-27ww-4gw4 — OpenClaw DM pairing-store identities could satisfy group allowlist authorization</title>
    <updated>2026-10-06T07:07:57.164639+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>## Summary
DM pairing-store identities were incorrectly eligible for group allowlist authorization checks, enabling cross-context authorization in group message paths.</p>
<p>## 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`.</p>
<p>This is an authorization-policy boundary issue between DM pairing and group allowlists.</p>
<p>## Affected Packages / Versions
- `openclaw` (npm): affected `&lt;= 2026.2.25` (latest published npm version at triage time)
- `openclaw` (npm): patched `&gt;= 2026.2.26` (planned next release)</p>
<p>## Fix Commit(s)
- `openclaw/openclaw@8bdda7a651c21e98faccdbbd73081e79cffe8be0`
- `openclaw/openclaw@051fdcc428129446e7c084260f837b7284279ce9`</p>
<p>## 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.</p>
<p>## 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.</p>
<p>OpenClaw thanks @tdjackey for reporting.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-jv6r-27ww-4gw4"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0586</id>
    <title>WID-SEC-W-2026-0586 — OpenClaw: Mehrere Schwachstellen</title>
    <updated>2026-10-06T07:07:57.164670+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0586"/>
  </entry>
</feed>
