CVE-2026-41358: OpenClaw · Slack thread context could include messages from non-allowlisted senders
Affects openclawSource GCVE Database
Not known to be exploited · CVSS 5.4 Medium : upgrade to 2026.4.2 when convenient.
Data as of 27 Oct 2026, 00:07 UTC
- Patch
- Available – fixed in 2026.4.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 4 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade openclaw to 2026.4.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmopenclaw | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
## Summary Before OpenClaw 2026.4.2, Slack thread starter and thread-history context fetched through the API was not filtered by the effective sender allowlist. Messages from non-allowlisted senders could still enter the agent context when an allowlisted user replied in the same thread. ## Impact A Slack deployment that relied on sender allowlists could still feed non-allowlisted thread content into the model context through thread history. This was a sender-access-control bypass on Slack thread context, not a direct channel-auth bypass. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.4.1` - Patched versions: `>= 2026.4.2` - Latest published npm version: `2026.4.1` ## Fix Commit(s) - `ac5bc4fb37becc64a2ec314864cca1565e921f2d` — filter Slack thread context by the effective allowlist ## Release Process Note The fix is present on `main` and is staged for OpenClaw `2026.4.2`. Publish this advisory after the `2026.4.2` npm release is live. OpenClaw thanks @AntAISecurityLab for reporting.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-qm77-8qjp-4vcm (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-41358 (opens in a new tab)
- github.com/openclaw/openclaw/commit/ac5bc4fb37becc64a2ec314864cca1565e921f2d (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- vulncheck.com/advisories/openclaw-sender-allowlist-bypass-via-slack-thread-context (opens in a new tab)