CVE-2026-1699CWE-829

In the Eclipse Theia Website repository, the GitHub Actions workflow .github/workflows/preview.yml used pull_request_target trigger while checking out and…

Critical · published January 30, 2026

CVSS v3.1
10.0
EPSS
1%
Percentile
45.8
In the wild
Unconfirmed
What it is

🚨 A crafty trigger in the Eclipse Theia GitHub Actions could let any user execute code in the CI environment, like a rogue chef in a restaurant kitchen! 🔥 Think of it like a restaurant that allows anyone to walk in and cook without checking their credentials. One poorly vetted recipe can lead to a disastrous dish that affects all diners—here, that dish is untrusted code running with full access to secrets and write permissions. An attacker could pull off a deception of epic proportions, gaining access to sensitive repository secrets, modifying the official Theia website, and publishing malicious packages under the Eclipse Theia organization. The consequences could be absolutely devastating—imagine the turmoil of having your project compromised, all because of a single misconfigured file!

Put simply

Think of it like a restaurant that allows anyone to walk in and cook without checking their credentials. One poorly vetted recipe can lead to a disastrous dish that affects all diners—here, that dish is untrusted code running with full access to secrets and write permissions. This vulnerability arises from the use of the `pull_request_target` trigger in the GitHub Actions workflow `.github/workflows/preview.yml`, which allows untrusted pull request code to execute with extensive repository permissions, including access to sensitive data.

What to do

An attacker could pull off a deception of epic proportions, gaining access to sensitive repository secrets, modifying the official Theia website, and publishing malicious packages under the Eclipse Theia organization. The consequences could be absolutely devastating—imagine the turmoil of having your project compromised, all because of a single misconfigured file! It's crucial to patch this immediately! Update the workflow to use a safer trigger like `pull_request` instead, review all repository access settings, and ensure that secrets are safeguarded. Consider implementing stricter code review practices for all pull requests. You've got this! Follow these steps and your repository will be locked down and secure in no time. 🛡️

The record
Technical detail
CVSS v3.1
10.0 · CRITICAL
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00560 · 45.8th percentile
Weakness
CWE-829 · Inclusion of Functionality from Untrusted Control Sphere
Published
2026-01-30T09:57Z
EPSS history
Timeline
  • 30 JAN 09:57Z
    In the Eclipse Theia Website repository, the GitHub Actions workflow .github/workflows/preview.yml used pull_request_target trigger while checking out and…
    cvelistv5