Skip to content
Applications

CVE-2026-60009

8.8
High
EPSS 0.37%Patch availableAug 5, 2026

Unauthenticated arbitrary file write in Eclipse Theia (<=1.73.1) via POST /file-upload.

common questions

Is CVE-2026-60009 being exploited?

Not confirmed. CVE-2026-60009 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.37% probability of exploitation in the next 30 days.

How severe is CVE-2026-60009?

CVE-2026-60009 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-60009?

Yes. A fix has been recorded for CVE-2026-60009. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-60009 affect?

CVE-2026-60009 affects Eclipse Theia <= 1.73.1 (browser deployments), @theia/filesystem backend, Web deployments with filesystem enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-60009?

Immediately restrict/disable /file-upload, enforce auth, block cross-origin requests, and upgrade when vendor patch is released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Eclipse Theia <= 1.73.1 (browser deployments)@theia/filesystem backendWeb deployments with filesystem enabled
impact

Unauthenticated HTTP multipart write of attacker-specified absolute paths outside workspace, enabling remote code execution (e.g., overwrite ~/.bashrc).

action required

Immediate action required

affected versions
Eclipse Foundation Eclipse Theia
  • affected< 1.74.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free