CVE-2026-60009: CSRF
In Eclipse Theia versions up to and including 1.73.1, the @theia/filesystem backend binds POST /file-upload in every filesystem-enabled deployment. The handler takes an attacker-supplied absolute path from the multipart uri field and calls fs.move(tmp, target, { overwrite: true }) with no workspace confinement and no authentication. In browser (non-Electron) deployments the connection token is enforced only on WebSocket upgrades; the HTTP middleware in @theia/core re-issues the cookie and calls next() without rejecting tokenless HTTP requests. Because multipart/form-data is a CORS-safelisted request type, a cross-origin web page can trigger the write with no preflight and no credentials, resulting in an unauthenticated arbitrary file write outside the workspace to any absolute path the backend process can write. This can escalate to remote code execution, for example by overwriting a startup-executed file such as ~/.bashrc. Electron mode uses a separate ElectronSecurityToken and is not affected via this path.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-60009?
The severity of CVE-2026-60009 is rated as high with a score of 8.8.
What types of vulnerabilities are associated with CVE-2026-60009?
CVE-2026-60009 is associated with CSRF and Path Traversal vulnerabilities.
How does CVE-2026-60009 affect Eclipse Theia users?
CVE-2026-60009 allows attackers to manipulate file paths in any filesystem-enabled deployment, potentially leading to unauthorized file access.
How do I fix CVE-2026-60009?
To fix CVE-2026-60009, upgrade Eclipse Theia to version 1.73.2 or later where the vulnerability is addressed.
What is the impact of exploiting CVE-2026-60009?
Exploiting CVE-2026-60009 could lead to unauthorized file operations and data exposure due to improper path handling.