CVE-2026-41358: OpenClaw Slack Thread Context Vulnerability Allows Non-Allowlisted Messages

openclaw Updated 05 May 2026

Summary

04/05/2026

Disclosed on

CVE-2026-41358

CVE

Yes i

Fix available

Low

Severity

5.4

CVSS Score

CVE-2026-41358: OpenClaw: Slack thread context could include messages from non-allowlisted senders. Affects openclaw versions < 2026.4.2. Fixed in 2026.4.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or Browse

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats

SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml

Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile

Javascript package-lock.json · yarn.lock · pnpm-lock.yaml

PHP composer.lock

Python poetry.lock · requirements.txt · Pipfile.lock

Go go.mod

Rust Cargo.lock

Ruby Gemfile.lock

Dart pubspec.lock

C/C++ conan.lock

Elixir mix.lock

Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Background

OpenClaw is an open-source package designed for integrating with Slack, enabling users to manage and interact with Slack threads effectively. It utilizes an allowlist mechanism to control which senders' messages are considered valid in the context of thread interactions. However, prior to version 2026.4.2, OpenClaw had a vulnerability that allowed messages from non-allowlisted senders to be included in the thread context, potentially compromising the intended access controls.

Vulnerability Detail

The vulnerability arises from the failure to filter Slack thread starter and thread-history context fetched through the API based on the effective sender allowlist. This means that if an allowlisted user replies in a thread, messages from non-allowlisted senders could still be included in the agent context. This represents a bypass of sender-access-control specifically for Slack thread context, which could lead to unintended exposure of sensitive information and compromise the integrity of the communication within Slack.

How To Fix

Latest published version: 2026.10.6 as of 22 Oct 2026

npm install openclaw@2026.10.6

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2026.4.2

This is the first release that contains the fix.

npm install openclaw@2026.4.2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can manually monitor and restrict the messages included in thread contexts until they can update to the patched version. However, this is not a long-term solution and updating the package is strongly recommended.

Conclusion

In summary, the vulnerability identified as CVE-2026-41358 in OpenClaw allows non-allowlisted messages to be included in Slack thread contexts, posing a risk to sender-access-control mechanisms. Users are advised to update to version 2026.4.2 or later to mitigate this issue effectively.

See every vulnerability recorded for openclaw →