https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 10:24:11 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32006 <p><strong>Affected:</strong> OpenClaw</p> <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> <p><strong>Affected:</strong> OpenClaw</p> <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> https://vulnerability.circl.lu/vuln/cve-2026-32006 https://vulnerability.circl.lu/vuln/ghsa-25pw-4h6w-qwvm <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&#39;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> <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&#39;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> https://vulnerability.circl.lu/vuln/ghsa-25pw-4h6w-qwvm