What is the CVSS score of CVE-2026-1699?

CVE-2026-1699 has a CVSS 3.1 base score of 10.0 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-1699?

Yes, a public proof-of-concept exploit is available for CVE-2026-1699. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-1699?

Within 24 hours: Immediately disable or restrict the affected preview.yml workflow to trusted contributors only; audit recent pull requests and GitHub Actions logs for suspicious activity; revoke any exposed credentials or tokens. Within 7 days: Implement mandatory code review requirements for all pull requests before merge; enable branch protection rules; conduct forensic analysis of workflow execution history. Within 30 days: Migrate to a patched version when available; implement separate CI/CD credentials with minimal privileges; deploy additional monitoring on GitHub Actions activity.

Theia Website CVE-2026-1699

CRITICAL

Inclusion of Functionality from Untrusted Control Sphere (CWE-829)

2026-01-30 emo@eclipse.org

Github Theia Website Eclipse

10.0

CVSS 3.1 · NVD

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Create malicious pull request
Delivery

GitHub Actions workflow checks out untrusted code
Exploit

Arbitrary code executes in CI environment
Execution

Access repository secrets and GITHUB_TOKEN
Impact

Exfiltrate credentials and modify repository

Vulnerability Assessment

Weakness	CWE CWE-829 OWASP Top 10:2025 A08:2025 - Software or Data Integrity Failures ASVS 5.0 V15 - Secure Coding and Architecture Trusted source inclusion only
Exploitation Conditions	Eclipse Theia GitHub repository with .github/workflows/preview.yml using pull_request_target trigger without code review gates. Attacker must have ability to submit pull requests to the repository. Default GitHub Actions permissions must include contents:write, packages:write, pages:write, actions:write.
Impact	CVSS 10.0. Eclipse Theia is a major IDE framework — supply chain compromise could affect downstream IDE distributions.
Exploit ScenarioDerived	Attacker submits malicious PR that modifies CI scripts, which execute in the Theia repo context with access to signing keys and deployment secrets.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

Supply chain vulnerability in Eclipse Theia GitHub Actions workflow. The preview.yml workflow uses pull_request_target with checkout, enabling malicious PRs to steal secrets. CVSS 10.0, PoC available.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 22:00 CVSS 10.0

GitHub Actions supply chain attack in Eclipse Theia.

RemediationAI

Fix GitHub Actions workflow to not checkout PR code with pull_request_target.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

CWE-829 in GitHub Actions. pull_request_target trigger runs in base repo context while checking out PR code, exposing repository secrets.

Know when Theia Website gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 10.0 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

PoC Detected

Mar 10, 2026 - 18:23 vuln.today

Public exploit code

CVE Published

Jan 30, 2026 - 10:15 nvd

CRITICAL 10.0

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A critical vulnerability in Eclipse Theia's GitHub Actions workflow allows attackers to execute arbitrary code in the CI/CD pipeline through malicious pull requests, potentially compromising source code, build artifacts, and deployment credentials. Any organization using Eclipse Theia for web-based development faces immediate risk of supply chain compromise and unauthorized access to sensitive systems.

Business Impact: Severe

Compensating Controls

Disable pull_request_target trigger immediately and switch to pull_request trigger with explicit checkout of base branch only; restrict GitHub Actions permissions to read-only; implement separate, isolated CI/CD environment with no access to production secrets or credentials; require manual approval for pull requests from external contributors; enable GitHub Actions audit logging and implement SIEM alerting for suspicious workflow executions; use repository secrets management to limit credential exposure; enforce branch protection rules requiring code review before merge.

Threat Intelligence Overview

EPSS Score

0.0%

Top 90% exploitable

Exploit

POC

Public exploit code exists

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

CRITICAL severity + public POC available

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.