https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-09-28T17:01:02.470340+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/cve-2026-31991 CVE-2026-31991 — OpenClaw < 2026.2.26 - Authorization Bypass via DM Pairing-Store Leakage in Signal Group Allowlist 2026-09-28T17:01:02.667353+00:00

Affected: OpenClaw

OpenClaw versions prior to 2026.2.26 contain an authorization bypass vulnerability where Signal group allowlist policy incorrectly accepts sender identities from DM pairing-store approvals. Attackers can exploit this boundary weakness by obtaining DM pairing approval to bypass group allowlist checks and gain unauthorized group access.

 https://vulnerability.circl.lu/vuln/ghsa-wm8r-w8pf-2v6w GHSA-wm8r-w8pf-2v6w — OpenClaw has Signal group allowlist authorization bypass via DM pairing-store leakage 2026-09-28T17:01:02.667484+00:00

Affected: npm: openclaw

### Summary In OpenClaw `2026.2.25`, Signal group authorization under `groupPolicy=allowlist` could accept sender identities sourced from DM pairing-store approvals. This allowed DM pairing approvals to leak into group allowlist evaluation.

### Impact This is an authorization-boundary weakness between DM pairing and group allowlist controls. A sender approved for DM pairing could pass group checks without explicit group allowlisting.

### Affected Packages / Versions - Package: `openclaw` (npm) - Latest published version affected: `2026.2.25` - Vulnerable range: `<= 2026.2.25` - Patched version (planned next release): `>= 2026.2.26`

### Fix OpenClaw now keeps DM pairing-store entries DM-only and enforces explicit group allowlist boundaries in shared DM/group policy resolution used by Signal and other channels.

### Fix Commit(s) - `8bdda7a651c21e98faccdbbd73081e79cffe8be0` - `64de4b6d6ae81e269ceb4ca16f53cda99ced967a`

### Release Process Note `patched_versions` is pre-set to the planned next release (`2026.2.26`). After npm publish of that version, this advisory is ready to publish without further content edits.

Thanks @tdjackey for reporting.