CVE-2026-24764 Vulnerability Analysis & Exploit Details

CVE-2026-24764
Vulnerability Scoring

3.7
/10
Moderate Risk

Exploiting CVE-2026-24764 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2026-24764 Details

Status: Analyzed

Published on: 19 Feb 2026, 07:17 UTC

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

CVE-2026-24764 Vulnerability Summary

CVE-2026-24764: OpenClaw (formerly Clawdbot) is a personal AI assistant users run on their own devices. In versions 2026.2.2 and below, when the Slack integration is enabled, channel metadata (topic/description) can be incorporated into the model's system prompt. Prompt injection is a documented risk for LLM-driven systems. This issue increases the injection surface by allowing untrusted Slack channel metadata to be treated as higher-trust system input. This issue has been fixed in version 2026.2.3.

Assessing the Risk of CVE-2026-24764

Access Complexity Graph

The exploitability of CVE-2026-24764 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-24764

This vulnerability, CVE-2026-24764, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-24764, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-24764, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-24764 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2026-24764 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-24764 does not impact system availability.

CVE-2026-24764 References

External References

CWE Common Weakness Enumeration

CWE-94

CAPEC Common Attack Pattern Enumeration and Classification

  • Code Injection CAPEC-242 An adversary exploits a weakness in input validation on the target to inject new code into that which is currently executing. This differs from code inclusion in that code inclusion involves the addition or replacement of a reference to a code file, which is subsequently loaded by the target and used as part of the code of some application.
  • Leverage Executable Code in Non-Executable Files CAPEC-35 An attack of this type exploits a system's trust in configuration and resource files. When the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • cpe:2.3:a:openclaw:openclaw:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:0.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:0.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:0.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta4:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta4:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2.0.0:beta5:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2.0.0:beta5:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11-3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11-3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.12-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.12-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.14-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.14-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.16-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.16-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.24-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.24-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5-1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5-1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5-2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5-2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.5-3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.5-3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.20:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.20:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.21:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.21:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.22:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.22:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.23:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.23:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.24:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.24:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.29:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.29:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.1.30:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.1.30:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openclaw:openclaw:2026.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openclaw:openclaw:2026.2.2:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2026-24764: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-3010 – Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in Microchip TimePictra allows Query Syst...
  • CVE-2026-2844 – Missing Authentication for Critical Function vulnerability in Microchip TimePictra allows Configuration/Environment Manipulation.This issue affects...
  • CVE-2025-13673 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to SQL Injection via the 'coupon_code' parameter in all ver...
  • CVE-2026-2471 – The WP Mail Logging plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.15.0 via deserialization of ...
  • CVE-2026-1542 – The Super Stage WP WordPress plugin through 1.0.1 unserializes user input via REQUEST, which could allow unauthenticated users to perform PHP Objec...