Skip to main content
CVE-2026-1699VulnerabilityPublished Updated

CVE-2026-1699: Eclipse Theia – Website · Untrusted Functionality Inclusion

Affects Eclipse Theia – WebsiteSource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical : upgrade to 2fb0cc4bfc372cfaef79feb4eebb6563778b2560 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2fb0cc4bfc372cfaef79feb4eebb6563778b2560
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade Eclipse Theia – Website to 2fb0cc4bfc372cfaef79feb4eebb6563778b2560.

Affected software

ProductAffectedFixed in
Eclipse FoundationEclipse Theia - WebsiteAffected
  • =0
Fixed in
  • 2fb0cc4bfc372cfaef79feb4eebb6563778b2560
GitHubEclipse Theia - Websitepkg:github/Eclipse Theia - WebsiteOther threatsAffected
  • =0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-1699, organizations should immediately audit and modify their GitHub Actions workflows to avoid using the pull_request_target trigger when executing untrusted code. Instead, use the pull_request trigger, which runs workflows in the context of the pull request branch without access to secrets. Restrict the permissions of GITHUB_TOKEN to the minimum necessary scopes, avoiding broad write permissions such as contents:write, packages:write, pages:write, and actions:write unless absolutely required. Implement environment protection rules and require manual approvals for workflows that access sensitive secrets. Use GitHub's secret scanning and monitoring tools to detect any unauthorized secret exposure. Isolate CI environments and use ephemeral runners to limit persistence of malicious code. Regularly rotate repository secrets and tokens to reduce the window of exploitation. Educate developers and maintainers about secure CI/CD practices and the risks of executing untrusted code with elevated privileges. Monitor repository activity for unusual pushes or package publications and prepare incident response plans to quickly address any compromise.

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.

References

Community reviews

Loading reviews…