Summary
OpenClaw's Signal reaction-only status events could, in limited cases, be enqueued before access checks
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.
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.
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.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32050? CVE-2026-32050 is a medium-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.24. It is fixed in 2026.2.25. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of openclaw are affected by CVE-2026-32050? openclaw (npm) versions <= 2026.2.24 is affected.
- Is there a fix for CVE-2026-32050? Yes. CVE-2026-32050 is fixed in 2026.2.25. Upgrade to this version or later.
- Is CVE-2026-32050 exploitable, and should I be worried? Whether CVE-2026-32050 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32050 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32050? Upgrade
openclawto 2026.2.25 or later.