Security readout for executives and security teams
Plain-English summary
OpenClaw before 2026.2.25 can let an unauthorised sender create reaction-status notification entries for sessions they should not access. The documented impact is limited integrity impact, not data theft or service outage.
Executive priority
Handle as a moderate-priority access-control fix. It does not appear to expose confidential data or cause outage, but it can undermine trust in session event integrity.
Technical view
This is a CWE-863 access-control bypass in signal reaction notification handling. The reaction-only path in event-handler.ts can enqueue signal reaction status lines before DM or group access validation. CVSS 4.0 is 6.3 with network attack vector, high complexity, no privileges, and no user interaction.
Likely exposure
Exposure is limited to OpenClaw deployments running versions before 2026.2.25, especially where untrusted users or external senders can interact with signal reaction flows.
Exploitation context
The source bundle does not show KEV listing or confirmed active exploitation. Exploitation is described as network-reachable but high complexity, with integrity impact only.
Researcher notes
Key facts are source-grounded: OpenClaw before 2026.2.25, CWE-863, CVSS 6.3, and reaction-only event path authorization order. No exploit procedure or exploitation evidence is provided in the bundle.
Mitigation direction
- Upgrade OpenClaw to 2026.2.25 or later.
- Review the GitHub advisory and patch commit before rollout.
- Prioritise internet-facing or multi-tenant OpenClaw deployments.
- Check vendor guidance if upgrade timing or backport needs are unclear.
Validation and detection
- Inventory OpenClaw versions across production, staging, and containers.
- Confirm all deployments are on 2026.2.25 or later.
- Review event-handler.ts for authorization before reaction-status enqueueing.
- Validate unauthorized senders cannot create reaction status events.
- Monitor logs for unexpected reaction-status events from unauthorized senders.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-32050 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N2.21.4VulnCheckVulnerability scoring details
Base CVSS 4.0 score
6.3MediumVector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-792q-qw95-f446)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.2.25 - Unauthorized Reaction Status Event Enqueue via Access Check BypassCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.