Security readout for executives and security teams
Plain-English summary
OpenClaw versions before 2026.2.25 can accept Slack reaction and pin events from senders who should be blocked by configured policies. This can let a restricted Slack user influence OpenClaw's system-event context, but the cited CVSS impact is limited to low integrity impact.
Executive priority
Treat as a moderate-priority access-control issue. Prioritize patching where OpenClaw Slack events affect automation, AI context, ticketing, approvals, or other workflows that rely on trusted sender policy enforcement.
Technical view
This is a CWE-863 authorization bypass in OpenClaw Slack reaction_* and pin_* non-message event handlers. Sender-policy checks were not consistently applied before adding these events to system-event context. The CVSS v4.0 score is 5.3 with low complexity and low privileges required.
Likely exposure
Exposure is likely limited to organizations running OpenClaw before 2026.2.25 with Slack integration enabled and sender policies, DM restrictions, or channel user allowlists relied on for trust boundaries.
Exploitation context
The bundle does not cite active exploitation, and KEV status is false. A plausible attacker would already have limited Slack-level access and use reaction or pin events to bypass OpenClaw sender controls.
Researcher notes
The evidence supports an authorization check gap, not remote code execution or data theft. Focus review on non-message Slack event paths, policy consistency, regression tests for restricted senders, and whether downstream workflows trust system-event context.
Mitigation direction
- Upgrade OpenClaw to 2026.2.25 or later.
- Review the GitHub advisory and patch commits for deployment-specific guidance.
- Audit Slack sender policies, DM restrictions, and channel allowlists.
- Review OpenClaw logs for reaction or pin events from restricted senders.
- Temporarily limit affected Slack integrations if upgrade cannot be completed quickly.
Validation and detection
- Inventory deployed OpenClaw versions and identify any release before 2026.2.25.
- Confirm reaction_* and pin_* handlers enforce sender-policy checks.
- In staging, verify restricted Slack senders cannot enter system-event context.
- Review recent system-event context entries for unauthorized reaction or pin sources.
- Confirm production is running the patched OpenClaw release.
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-32899 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
- 5.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4VulnCheckVulnerability scoring details
Base CVSS 4.0 score
5.3MediumVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/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-rm2p-j3r7-4x4j)CVE reference, VulnCheck · vendor-advisory
- Patch Commit #1CVE reference, VulnCheck · patch
- Patch Commit #2CVE reference, VulnCheck · patch
- VulnCheck Advisory: OpenClaw < 2026.2.25 - Sender Policy Bypass in Slack Reaction and Pin Event HandlersCVE 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.