Model-context injection via unfiltered Slack threads
Published Apr 23, 2026 · Updated Apr 23, 2026
Origin validation error in Slack thread context in OpenClaw before 2026.4.2 allows attackers to inject messages into model context. The Slack message handler fetches the thread starter and reply history through the API but adds them to agent context without applying the effective sender allowlist. Attackers must place content in a thread that an allowlisted user replies to; the content can influence model processing but does not bypass channel authentication.
Summary
What happened
Origin validation error in Slack thread context in OpenClaw before 2026.4.2 allows attackers to inject messages into model context. The Slack message handler fetches the thread starter and reply history through the API but adds them to agent context without applying the effective sender allowlist. Attackers must place content in a thread that an allowlisted user replies to; the content can influence model processing but does not bypass channel authentication.
The record
- CVE
- CVE-2026-41358
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- OpenClaw Foundation
- Product
- OpenClaw
- Classifications
- CWE-346, T1659
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.4.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo