1. Home
  2. Vulnerabilities
  3. CVE-2026-1699
10.0
CRITICAL CVSS 3.1
CVE-2026-1699
Eclipse Theia GitHub Actions Code Execution Vulnerability
Description

In the Eclipse Theia Website repository, the GitHub Actions workflow .github/workflows/preview.yml used pull_request_target trigger while checking out and executing untrusted pull request code. This allowed any GitHub user to execute arbitrary code in the repository's CI environment with access to repository secrets and a GITHUB_TOKEN with extensive write permissions (contents:write, packages:write, pages:write, actions:write). An attacker could exfiltrate secrets, publish malicious packages to the eclipse-theia organization, modify the official Theia website, and push malicious code to the repository.

INFO

Published Date :

Jan. 30, 2026, 10:15 a.m.

Last Modified :

March 10, 2026, 6:23 p.m.

Remotely Exploit :

Yes !

Source :

[email protected]
Affected Products

The following products are affected by CVE-2026-1699 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Eclipse theia_website
: Total Affected Vendor : 1 | Products : 1
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 CRITICAL e51fbebd-6053-4e49-959f-1b94eeb69a2c
CVSS 3.1 CRITICAL [email protected]
CVSS 3.1 HIGH [email protected]
Solution
Reconfigure GitHub Actions to avoid pull_request_target trigger with untrusted code.
  • Avoid pull_request_target trigger for untrusted code.
  • Use pull_request trigger instead.
  • Validate pull request sources carefully.
  • Limit token permissions.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-1699.

URL Resource
https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/332 ExploitIssue TrackingVendor Advisory
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-1699 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-1699 weaknesses.

CAPEC-175: Code Inclusion Code Inclusion CAPEC-201: Serialized Data External Linking Serialized Data External Linking CAPEC-228: DTD Injection DTD Injection CAPEC-251: Local Code Inclusion Local Code Inclusion CAPEC-252: PHP Local File Inclusion PHP Local File Inclusion CAPEC-253: Remote Code Inclusion Remote Code Inclusion CAPEC-263: Force Use of Corrupted Files Force Use of Corrupted Files CAPEC-538: Open-Source Library Manipulation Open-Source Library Manipulation CAPEC-549: Local Execution of Code Local Execution of Code CAPEC-640: Inclusion of Code in Existing Process Inclusion of Code in Existing Process CAPEC-660: Root/Jailbreak Detection Evasion via Hooking Root/Jailbreak Detection Evasion via Hooking CAPEC-695: Repo Jacking Repo Jacking CAPEC-698: Install Malicious Extension Install Malicious Extension

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-1699 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2026-1699 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Mar. 10, 2026

    Action Type Old Value New Value
    Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    Added CPE Configuration OR *cpe:2.3:a:eclipse:theia_website:*:*:*:*:*:*:*:* versions up to (excluding) 2026-01-22
    Added Reference Type Eclipse Foundation: https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/332 Types: Exploit, Issue Tracking, Vendor Advisory
  • New CVE Received by [email protected]

    Jan. 30, 2026

    Action Type Old Value New Value
    Added Description In the Eclipse Theia Website repository, the GitHub Actions workflow .github/workflows/preview.yml used pull_request_target trigger while checking out and executing untrusted pull request code. This allowed any GitHub user to execute arbitrary code in the repository's CI environment with access to repository secrets and a GITHUB_TOKEN with extensive write permissions (contents:write, packages:write, pages:write, actions:write). An attacker could exfiltrate secrets, publish malicious packages to the eclipse-theia organization, modify the official Theia website, and push malicious code to the repository.
    Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
    Added CWE CWE-829
    Added Reference https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/332
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 10
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact