CVE-2026-60009
Last modified
CVE-2026-60009 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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. EPSS estimates a 0.30% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Eclipse | Theia | < 1.74.0 |
References
- https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/595Exploit, Mitigation, Vendor Advisory
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/595Exploit, Mitigation, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-60009?
How severe is CVE-2026-60009?
How do I fix CVE-2026-60009?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-6000A vulnerability was found in code-projects Online Library Ma…4.3
- CVE-2026-60000sshd in OpenSSH before 10.4 allows remote attackers to cause…7.5
- CVE-2026-60001sshd in OpenSSH before 10.4 does not always honor the minimu…6.5
- CVE-2026-60002ssh in OpenSSH before 10.4 can have a use-after-free when a …9.4
- CVE-2026-60005NGINX Plus and NGINX Open Source have a vulnerability in the…8.2
- CVE-2026-60007In Eclipse Milo versions 0.6.0 through 1.1.4, username-token…7.4
- CVE-2026-6001Authorization bypass through User-Controlled key vulnerabili…8.8
- CVE-2026-60011Sharp and Toshiba Tec MFPs (multifunction printers) fail to …6.9
- CVE-2026-6002Improper neutralization of Script-Related HTML tags in a web…8.8
- CVE-2026-60023Exposure of Sensitive Information to an Unauthorized Actor v…7.5
- CVE-2026-60024Joomla Extension - joomdonation.com - Insecure default confi…9.8
- CVE-2026-60025Joomla Extension - joomdonation.com - User enumeration in Ev…8.8
Are you affected by CVE-2026-60009?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
