CVE-2026-24764 is a low-severity (CVSS 3.7) CWE-74 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw has Remote Code Execution via System Prompt Injection in Slack Channel Descriptions
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-24764.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
Summary
When the Slack integration is enabled, Slack channel metadata (topic/description) could be incorporated into the model's system prompt.
Impact
Prompt injection is a documented risk for LLM-driven systems. This issue increased the injection surface by allowing untrusted Slack channel metadata to be treated as higher-trust system input.
This is relevant only for deployments that enable Slack. In deployments where tool execution is enabled, a successful injection could lead to unintended tool invocations and/or unintended data exposure.
Affected Packages / Versions
- npm:
openclaw< 2026.2.3
Patched Versions
- npm:
openclaw>= 2026.2.3
Mitigation
- If you do not use Slack: no action required.
- If you use Slack: upgrade to a patched version.
Fix Commit(s)
- 35eb40a7000b59085e9c638a80fd03917c7a095e
Thanks @KonstantinMirin for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.2.3npm install openclaw@2026.2.3 |
Affected Products
openclawopenclawDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-24764 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-24764 in your dependencies?
Find it across npm, including transitive dependencies.