Skip to content

OpenClaw: Slack system events bypass sender authorization in member and message subtype handlers

Moderate severity GitHub Reviewed Published Feb 26, 2026 in openclaw/openclaw

Package

npm openclaw (npm)

Affected versions

<= 2026.2.25

Patched versions

2026.2.26

Description

Summary

Slack member_* and message subtype system events (message_changed, message_deleted, thread_broadcast) were not consistently enforcing sender authorization before enqueueing system events.

Affected Packages / Versions

  • Package: openclaw (npm)
  • Latest published version: 2026.2.25
  • Affected range: <= 2026.2.25
  • Planned patched version: 2026.2.26 (pre-set for publish-readiness)

Technical Details

Slack system-event handlers in src/slack/monitor/events/members.ts and src/slack/monitor/events/messages.ts enqueued events after channel checks without shared sender authorization. Deployments relying on Slack DM allowlists (dmPolicy / allowFrom) or per-channel users allowlists could receive unauthorized system-event ingress from non-allowlisted senders.

The fix routes those handlers through authorizeAndResolveSlackSystemEventContext(...) and fails closed when message subtype sender identity cannot be resolved.

Fix Commit(s)

  • 3d30ba18a2aba1e1b302e77ff33145c3b06c01c8

Release Process Note

patched_versions is pre-set to >= 2026.2.26 so once npm 2026.2.26 is published, this advisory can be published without further field edits.

Thanks @tdjackey for reporting.

References

@steipete steipete published to openclaw/openclaw Feb 26, 2026
Published to the GitHub Advisory Database Mar 12, 2026
Reviewed Mar 12, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS score

Weaknesses

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. Learn more on MITRE.

CVE ID

No known CVE

GHSA ID

GHSA-v8cg-4474-49v8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.