Skip to main content

Eclipse Theia CVE-2026-82217

| EUVDEUVD-2026-68519 HIGH
Path Traversal (CWE-22)
2026-08-31 eclipse GHSA-2qmg-qr8r-hr5c
8.8
CVSS 3.1 · Vendor: eclipse
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker embeds prompt injection payload in external content
  2. Delivery
    Victim loads content into Theia AI Agent Mode session
  3. Exploit
    LLM generates crafted out-of-workspace file path targeting sensitive OS file
  4. Execution
    writeFileContent resolves path without workspace-containment check
  5. Persist
    Malicious content written silently to host filesystem (e.g., ~/.ssh/authorized_keys)
  6. Impact
    Attacker authenticates to backend host via planted SSH key

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires Eclipse Theia 1.73.0-1.74.x to be running with AI Agent Mode active and the victim to be engaged in an active Agent Mode session at the time the malicious content is processed. The vulnerability exists specifically in the writeFileContent, suggestFileContent, and associated replacement and state helper tools - non-Agent AI chat interactions that do not invoke these tools are not affected. The indirect prompt injection vector requires the victim to load attacker-influenced content into the agent's context, such as opening a repository with adversarial instructions embedded in files, fetching a crafted external resource, or processing third-party documentation. The CVSS vector specifies PR:N (no attacker authentication required against the Theia instance) and UI:R (the user must actively engage Agent Mode). Key limiting factors: the attack depends on successful indirect prompt injection, which is constrained by model instruction-following behavior and system prompt hardening; exploitation is further bounded by the backend OS user's privilege level - a least-privilege service account without SSH directory write access substantially reduces worst-case impact.

Impact

The official CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a scenario where an external attacker influences model path selection through indirect prompt injection, requiring only that the victim use Agent Mode. However, AC:L may overstate practical exploitability: successful exploitation requires Agent Mode to be active AND a prompt injection payload that survives the model's instruction filtering, which introduces real-world friction beyond what AC:L captures - AC:H is arguably more precise. No EPSS score was provided in the input intelligence, so exploitation probability is inferred rather than measured. This CVE is absent from the CISA KEV catalog, confirming no known active exploitation at time of analysis. No public proof-of-concept code has been identified. Despite the moderate real-world probability, the worst-case impact - silent write to ~/.ssh/authorized_keys yielding backend SSH access - is severe and warrants prompt patching wherever Theia runs in a networked or multi-user environment with AI features enabled.

Exploit ScenarioDerived

An attacker embeds adversarial prompt injection instructions inside a file or repository resource that a developer loads into Theia's AI Agent Mode context - for example, a crafted README.md, a malicious code comment, or a fetched web page. The injected instruction directs the LLM to invoke writeFileContent with a path of ~/.ssh/authorized_keys and an attacker-controlled SSH public key as content. Because Agent Mode applies the write without a confirmation dialog, the key is written silently, and the attacker subsequently obtains SSH access to the backend host under the Theia backend OS user's account. No public proof-of-concept for this specific CVE has been identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 31, 2026

Path traversal in Eclipse Theia 1.73.0-1.74.x AI Agent Mode allows arbitrary file writes outside the workspace with backend OS user privileges through model-supplied paths that bypass workspace-containment checks. The affected tools - writeFileContent, suggestFileContent, and associated replacement and state helpers - accept relative paths such as ../.bashrc, absolute paths, or tilde-expanded paths like ~/.ssh/authorized_keys without boundary validation. Because path arguments derive from LLM output, an indirect prompt injection attack embedded in developer-loaded content can steer writes to host-executed files and escalate to backend code execution; Agent Mode applies writes silently with no confirmation dialog. No public exploit code or CISA KEV listing exists at time of analysis, though the prompt-injection attack surface is realistic in cloud IDE deployments.

RemediationAI

Upgrade to Eclipse Theia 1.75.0 or later, which incorporates the fix in commit 28da106c254 (https://github.com/eclipse-theia/theia/commit/28da106c254); this replaces the broken per-tool path handling with the unified resolveAccessiblePath method. Adopters who implemented custom AI tools using the old ensureWithinWorkspace or resolveRelativePath APIs must migrate to resolveAccessiblePath as noted in the 1.75.0 CHANGELOG. If an immediate upgrade is not feasible, disable AI Agent Mode in the Theia configuration to remove the attack surface entirely - this eliminates all AI-assisted file editing capabilities as a side effect. As an OS-level compensating control, run the Theia backend process as a minimal-privilege user without write access to ~/.ssh, shell startup files, or cron directories; this reduces worst-case impact but does not prevent writes to arbitrary paths within the backend user's accessible filesystem. Consult the Eclipse advisory at https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/624 for official guidance.

Affected VersionsENISA

Eclipse Theia 1.73.0 <1.75.0

Affected Packages

euvd eclipse_theia fix: 1.75.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Eclipse Theia is an extensible cloud and desktop IDE framework (CPE: cpe:2.3:a:eclipse_foundation:eclipse_theia:*:*:*:*:*:*:*:*) whose AI Agent Mode exposes file-change tools that invoke backend filesystem APIs. The root cause is CWE-22 (Improper Limitation of a Pathname to a Restricted Directory): functions resolveRelativePath and ensureWithinWorkspace were applied inconsistently or bypassed entirely across the file-change tool suite, allowing model-supplied strings to resolve to arbitrary OS paths. The fix in commit 28da106c254 replaces the fragmented per-tool approach with a centralized resolveAccessiblePath method enforcing workspace-root containment and honoring the ai-features.workspaceFunctions.allowedExternalPaths preference and a new AccessibleRootContribution extension point. The indirect prompt injection channel is the core attack surface: any attacker-influenced document, repository file, or web resource loaded into the agent context can carry adversarial instructions that steer the LLM's tool invocations toward crafted out-of-workspace paths.

Know when Eclipse Theia gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (eclipse) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 7.5 HIGH

AC:H reflects the practical requirement for successful indirect prompt injection steering model output to a crafted path; all other metrics align with the provided vector.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (eclipse).

CVSS VectorVendor: eclipse

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Aug 31, 2026 - 15:17 EUVD
CVE Published
Aug 31, 2026 - 13:40 cve.org
HIGH 8.8

DescriptionCVE.org

In Eclipse Theia versions 1.73.0 up to but not including 1.75.0, the AI "Agent Mode" file-change tools (writeFileContent, suggestFileContent, and the replacement and state helpers) resolved a model-supplied file path without a workspace-containment check. A crafted relative path such as ../.bashrc, an absolute path, or a ~-expanded path could therefore write or delete files outside the workspace with the privileges of the Theia backend OS user. Because the path argument is influenced by model output, it can be steered through indirect prompt injection, and in Agent Mode writes are applied without a confirmation dialog. Writing to a host-executed file such as a shell startup file or ~/.ssh/authorized_keys can escalate to code execution on the backend.

Executive ViewAI

Why It Matters

Eclipse Theia 1.73.0-1.74.x AI Agent Mode contains a path traversal vulnerability (CVE-2026-82217, CVSS 8.8) enabling arbitrary file writes to sensitive system locations through prompt injection in developer-loaded content; no public exploit identified at time of analysis. Organizations deploying Theia as a cloud IDE face significant risk of infrastructure compromise if developers access untrusted sources, potentially enabling backend code execution and system compromise.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: Disable AI Agent Mode if not operationally critical; restrict backend OS user filesystem permissions via AppArmor or SELinux to deny writes outside workspace directory; implement filesystem access monitoring on sensitive paths (~/.ssh, /etc, backend user home); disable file-write operations in Theia configuration; sandbox Theia backend processes in isolated containers with minimal host privilege; implement egress filtering to limit Agent Mode's network reach.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Low
cloud IDE framework serving niche developer-tooling deployments
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy