Eclipse Foundation Eclipse Theia
In Eclipse Theia versions 1.66.0 and up until including 1.73.1, the `@theia/plugin-ext` backend exposes the `/hostedPlugin/:pluginId/:path(*)` HTTP endpoint, which resolves the requested file path with `path.resolve(localPath, filePath)` without verifying that the resolved path stays within the plugin's directory. An unauthenticated network attacker can send percent-encoded `../` sequences (`%2e%2e%2f`) that decode into the path parameter and escape the plugin directory, allowing arbitrary files readable by the Theia backend process to be retrieved. Plugin IDs are derived deterministically from a plugin's publisher and name, so built-in plugins serve as reliable anchors that require no prior knowledge of the target system.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 1.66.0, < 1.74.0
Fixed in 1.74.0
Mitigation
Upgrade Eclipse Theia to 1.74.0 or later.
References
- Vendor advisory github.com/eclipse-theia/theia/security/adviso…
Timeline
Days relative to CVE publicationFirst public PoC 36 days after publication; not in CISA KEV. First PoC: nuclei template: Eclipse Theia - Unauthenticated Path Traversal (nuclei template, 10 Sep 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Eclipse Theia - Unauthenticated Path Traversal | 10 Sep 2026 | 14 Nov 2026 |