<?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-06T04:43:35.344009+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-32006</id>
    <title>BREW-openclaw-cli-CVE-2026-32006 — OpenClaw has a BlueBubbles group allowlist mismatch via DM pairing-store fallback</title>
    <updated>2026-10-06T04:43:35.347895+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: openclaw-cli</p>
<p>### Summary
In `openclaw@2026.2.25`, BlueBubbles group authorization could incorrectly treat DM pairing-store identities as group allowlist identities when `dmPolicy=pairing` and `groupPolicy=allowlist`.</p>
<p>A sender that was only DM-paired (not explicitly present in `groupAllowFrom`) could pass group sender checks for message and reaction ingress.</p>
<p>Per OpenClaw's `SECURITY.md` trust model, this is a constrained authorization-consistency issue, not a multi-tenant boundary bypass or host-privilege escalation.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published npm version at triage time: `2026.2.25`
- Affected versions: `&lt;= 2026.2.25`
- Patched versions: `&gt;= 2026.2.26` (planned next release)</p>
<p>### Technical Details
Root cause was DM/group allowlist composition where DM pairing-store identities could flow into group authorization decisions.</p>
<p>Fix approach:
- centralize DM/group authorization composition via shared resolvers
- remove local DM/group list recomposition at channel callsites
- add cross-channel regression coverage for message + reaction ingress
- add CI guard to block future pairing-store leakage into group auth composition</p>
<p>### Impact
- Affects deployments using BlueBubbles with `groupPolicy=allowlist` and `dmPolicy=pairing` when pairing-store entries are present.
- Could allow DM-authorized identities to be treated as group-authorized without explicit `groupAllowFrom` membership.
- Does **not** bypass gateway auth, sandbox boundaries, or c…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-openclaw-cli-cve-2026-32006"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2026-14837</id>
    <title>cnvd-2026-14837</title>
    <updated>2026-10-06T04:43:35.347963+00:00</updated>
    <content>cnvd-2026-14837</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2026-14837"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-329403</id>
    <title>EUVD-2026-329403</title>
    <updated>2026-10-06T04:43:35.347981+00:00</updated>
    <content>EUVD-2026-329403</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-329403"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-32006</id>
    <title>fkie_cve-2026-32006</title>
    <updated>2026-10-06T04:43:35.347994+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 treated as group allowlist identities when dmPolicy=pairing and groupPolicy=allowlist. Remote attackers can send messages and reactions as DM-paired identities without explicit groupAllowFrom membership to bypass group sender authorization checks.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-32006"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-25pw-4h6w-qwvm</id>
    <title>GHSA-25pw-4h6w-qwvm — OpenClaw has a BlueBubbles group allowlist mismatch via DM pairing-store fallback</title>
    <updated>2026-10-06T04:43:35.348016+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: openclaw</p>
<p>### Summary
In `openclaw@2026.2.25`, BlueBubbles group authorization could incorrectly treat DM pairing-store identities as group allowlist identities when `dmPolicy=pairing` and `groupPolicy=allowlist`.</p>
<p>A sender that was only DM-paired (not explicitly present in `groupAllowFrom`) could pass group sender checks for message and reaction ingress.</p>
<p>Per OpenClaw's `SECURITY.md` trust model, this is a constrained authorization-consistency issue, not a multi-tenant boundary bypass or host-privilege escalation.</p>
<p>### Affected Packages / Versions
- Package: `openclaw` (npm)
- Latest published npm version at triage time: `2026.2.25`
- Affected versions: `&lt;= 2026.2.25`
- Patched versions: `&gt;= 2026.2.26` (planned next release)</p>
<p>### Technical Details
Root cause was DM/group allowlist composition where DM pairing-store identities could flow into group authorization decisions.</p>
<p>Fix approach:
- centralize DM/group authorization composition via shared resolvers
- remove local DM/group list recomposition at channel callsites
- add cross-channel regression coverage for message + reaction ingress
- add CI guard to block future pairing-store leakage into group auth composition</p>
<p>### Impact
- Affects deployments using BlueBubbles with `groupPolicy=allowlist` and `dmPolicy=pairing` when pairing-store entries are present.
- Could allow DM-authorized identities to be treated as group-authorized without explicit `groupAllowFrom` membership.
- Does **not** bypass gateway auth, sandbox boundaries, or c…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-25pw-4h6w-qwvm"/>
  </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-06T04:43:35.348052+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>
