Skip to content

OpenClaw Affected by Remote Code Execution via System Prompt Injection in Slack Channel Descriptions

Low severity GitHub Reviewed Published Feb 14, 2026 in openclaw/openclaw • Updated Feb 19, 2026

Package

npm openclaw (npm)

Affected versions

< 2026.2.3

Patched versions

2026.2.3

Description

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.

References

@steipete steipete published to openclaw/openclaw Feb 14, 2026
Published to the GitHub Advisory Database Feb 17, 2026
Reviewed Feb 17, 2026
Published by the National Vulnerability Database Feb 19, 2026
Last updated Feb 19, 2026

Severity

Low

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
High
Privileges required
Low
User interaction
Required
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:H/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(10th percentile)

Weaknesses

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. Learn more on MITRE.

Improper Control of Generation of Code ('Code Injection')

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. Learn more on MITRE.

CVE ID

CVE-2026-24764

GHSA ID

GHSA-782p-5fr5-7fj8

Source code

Credits

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