CVE-2026-44688: Eclipse Theia AI Chat Prompt Injection – Arbitrary Code Execution Risk
Eclipse Theia's AI chat assistant has a critical flaw where it treats file and directory names as if they were legitimate instructions rather than user data. An attacker can create a malicious code repository with specially crafted folder or file names that trick the AI into following hidden commands embedded in those names. This could lead to sensitive data being stolen or unauthorized commands being executed on a developer's machine, especially when developers open untrusted repositories in Theia.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.8 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Weaknesses (CWE)
- CWE-829
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-18 / 2026-06-22
NVD description (verbatim)
In Eclipse Theia versions prior to 1.71.0, the AI chat agent processed workspace file and directory names as part of its prompt context without distinguishing them from system instructions. An attacker could craft a malicious repository with adversarial directory or file names that, when analyzed by the AI agent, would cause the agent to follow attacker-controlled instructions (indirect prompt injection). Combined with other AI chat features available in untrusted workspaces, this enabled attack chains leading to data exfiltration via Markdown image rendering or arbitrary command execution via task definitions.
1 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-44688 is a prompt injection vulnerability in Eclipse Theia's AI chat agent. The vulnerability exists because the agent includes workspace file and directory names directly in its prompt context without sanitization or clear semantic separation from system-level instructions. An attacker can exploit this by creating a repository with adversarial filenames or directory names that, when processed by the AI agent, are interpreted as instructions rather than benign data. The attack is compounded by integration with other Theia features: Markdown image rendering can exfiltrate data via external image requests, and task definitions can achieve arbitrary command execution. The vulnerability affects Theia versions prior to 1.71.0 and requires user interaction (opening a repository) but does not require elevated privileges.
Business impact
This vulnerability poses a significant risk to development teams using Eclipse Theia with AI-assisted coding workflows. Threat actors can distribute trojanized repositories that compromise developer machines when opened, leading to theft of source code, API keys, credentials stored in the workspace, or environment variables. In supply chain scenarios, a compromised developer environment could facilitate lateral movement into broader organizational networks. The low barrier to exploitation—requiring only that a developer clone and open a malicious repository—makes this particularly dangerous in collaborative environments where developers routinely work with code from multiple sources.
Affected systems
Eclipse Theia versions prior to 1.71.0 are affected. The vulnerability is specifically triggered when the AI chat agent is active and processes workspace contents. Organizations running older versions of Theia or bundled Theia installations (such as in cloud IDEs or custom development environments) should verify their version against 1.71.0. Browser-based and desktop deployments of Theia are both in scope.
Exploitability
The vulnerability is readily exploitable with low complexity. An attacker needs only to create a repository with crafted filenames and distribute it (via GitHub, GitLab, or other code hosting platforms, or via social engineering). No special network access, authentication, or system-level privileges are required. User interaction is mandatory—a developer must clone and open the repository in Theia for the AI agent to process the malicious filenames—but this is a normal development workflow. The CVSS vector reflects this accessibility: network-based attack, low complexity, no privileges required, and user interaction present.
Remediation
Upgrade Eclipse Theia to version 1.71.0 or later. This version includes fixes that properly sanitize and contextualize file and directory names within AI chat prompts, preventing them from being interpreted as instructions. Organizations should also consider disabling AI chat features in Theia if they are not actively used, and educating developers about the risks of opening untrusted repositories in code editors with AI-assisted features enabled.
Patch guidance
Apply the upgrade to Eclipse Theia 1.71.0 or later as soon as possible. If you are using Theia as part of a larger platform (cloud IDE, container image, or customized distribution), verify with your vendor that they have updated their Theia dependencies. Test the upgrade in a non-production environment first to ensure compatibility with extensions and custom configurations. If immediate patching is not feasible, consider disabling the AI chat agent feature until the patch can be deployed.
Detection guidance
Monitor for access to Theia instances from suspicious or unexpected code repositories. Log and review any AI chat interactions that reference file or directory names containing unusual syntax, command-like patterns, or special characters that might indicate prompt injection attempts. If you have telemetry from Theia or IDE usage, look for unusual patterns in which workspaces are opened or analyzed. Endpoint detection and response (EDR) tools should monitor for unexpected command execution or process spawning originating from Theia or task execution contexts. Network monitoring can flag data exfiltration attempts via external image requests generated from Markdown rendering within AI chat outputs.
Why prioritize this
This vulnerability merits immediate attention due to its combination of high severity (CVSS 8.8), ease of exploitation, and direct impact on developer security. Unlike many supply chain risks, this does not require a compromised legitimate package—it exploits normal developer workflows. The potential for data exfiltration and arbitrary code execution makes it critical for any organization where developers use Theia with AI features. The lack of CISA KEV status should not reduce urgency; this is a recent disclosure with high real-world applicability.
Risk score, explained
The CVSS 3.1 score of 8.8 (HIGH) reflects: network-based attack vector (any internet-distributed repository can be malicious), low attack complexity (simple filename crafting), no privileges required, user interaction necessary (developer must open the repo), limited scope (confined to the affected system), and high impact across confidentiality, integrity, and availability (data theft, code execution, system compromise). The score accurately captures the severity while acknowledging that user action is required.
Frequently asked questions
Do I need to have actively used Theia's AI chat feature for this to affect me?
Yes, the vulnerability is triggered when the AI chat agent processes your workspace. If you have Theia installed but have never used or activated the AI chat feature, you are not directly affected by this prompt injection. However, if you open an untrusted repository in any Theia instance where AI chat is enabled (even if dormant), the risk materializes if the agent processes the filenames.
Can this vulnerability be exploited if I just clone a malicious repository without opening it in Theia?
No. The vulnerability requires that the repository be opened in Eclipse Theia and that the AI chat agent processes the workspace contents. Simply having the malicious files on your system does not trigger the vulnerability. However, this emphasizes the danger: developers commonly clone repositories and open them immediately, making this a very practical attack vector.
What types of data are most at risk if I'm compromised?
Anything in your workspace and environment is at risk. This includes source code, configuration files, environment variables (which often contain API keys, database credentials, and tokens), private keys stored in .ssh or .env files, and any data the AI agent can access or that flows through Markdown rendering in chat responses. The scope depends on what permissions the developer account has in your organization.
If I've already upgraded to Theia 1.71.0, am I fully protected?
Upgrading to 1.71.0 or later patches the prompt injection vulnerability itself. However, security is layered. You should still practice general caution when cloning code from unfamiliar sources and consider using separate development environments for untrusted code. Additionally, ensure that any custom Theia extensions or integrations you use are also kept up to date.
This analysis is based on the CVE record and published vulnerability data available as of the modification date (2026-06-22). While we have made reasonable efforts to ensure accuracy, this explainer is provided for informational purposes and should not be considered professional security advice for your specific environment. Organizations should verify patch availability and compatibility with their exact Theia deployment before applying updates. If you discover active exploitation or believe you have been compromised, contact your security incident response team or a qualified cybersecurity professional immediately. SEC.co makes no warranty regarding the completeness or applicability of this information to your systems. Source: NVD (public-domain), retrieved 2026-07-27. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-44691HIGHEclipse Theia Arbitrary Code Execution via Untrusted Task Execution
- CVE-2026-46580HIGHEclipse Theia AI Prompt Injection – Patch to 1.71.0
- CVE-2026-22551MEDIUMEclipse Theia AI Chat Information Disclosure via Markdown Rendering
- CVE-2022-49036HIGHSynology Active Backup for Business Recovery Media Creator Arbitrary Code Execution
- CVE-2022-49042HIGHSynology Hyper Backup Explorer Arbitrary Code Execution via MinGW DLL
- CVE-2026-11269HIGHChrome Extension Sandbox Escape (v149)
- CVE-2026-12057HIGHFoxit AI Sandbox Escape Arbitrary Code Execution Vulnerability
- CVE-2026-22283HIGHDell PowerFlex Manager Unauthenticated Information Disclosure Vulnerability