CVE-2026-32050: OpenClaw's Signal reaction-only status events could, in limited cases, be enqueued before access checks
Summary In a narrow Signal reaction-notification path, reaction-only inbound events could enqueue a status event before sender access checks were applied. Affected Packages / Versions - Package: openclaw (npm) - Affected: <= 2026.2.24 (latest published at patch time) - Fixed: 2026.2.25 Details In the affected flow (src/signal/monitor/event-handler.ts), reaction-only handling could return after…
Published Mar 3, 2026 · Updated Mar 30, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.24
- Fixed in
- 2026.2.25
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
In a narrow Signal reaction-notification path, reaction-only inbound events could enqueue a status event before sender access checks were applied.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
<= 2026.2.24(latest published at patch time) - Fixed:
2026.2.25
Details
In the affected flow (src/signal/monitor/event-handler.ts), reaction-only handling could return after enqueueSystemEvent(...) before DM/group authorization checks were evaluated for that sender.
This behavior was limited to reaction-only inbound events with reaction notifications enabled. In that case, a sender not authorized for normal DM flow could still queue a Signal reaction status line for that session.
The fix applies shared DM/group access checks before reaction notification enqueue. Pairing behavior for normal DM messages is unchanged.
Impact
- Limited to Signal reaction-only inbound events.
- Could add an unauthorized reaction status line to agent context for affected sessions.
- Did not directly enable normal DM delivery or direct host command execution.
Fix Commit(s)
2aa7842adeedef423be7ce283a9144b9f1a0a669
Release Process Note
patched_versions is pre-set to 2026.2.25 so once npm release is out, advisory publish can proceed directly.
OpenClaw thanks @tdjackey for reporting.
Credited to tdjackey.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-792q-qw95-f446
- https://github.com/openclaw/openclaw/commit/2aa7842adeedef423be7ce283a9144b9f1a0a669
- https://nvd.nist.gov/vuln/detail/CVE-2026-32050
- https://www.vulncheck.com/advisories/openclaw-unauthorized-reaction-status-event-enqueue-via-access-check-bypass
- https://github.com/advisories/GHSA-792q-qw95-f446
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
