Skip to content
Cloud

CVE-2026-1699

10.0
Critical
EPSS 0.51%Patch availableJan 30, 2026

PR-targeted GitHub Actions flow enables remote code execution in CI, exposing secrets.

common questions

Is CVE-2026-1699 being exploited?

Not confirmed. CVE-2026-1699 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.51% probability of exploitation in the next 30 days.

How severe is CVE-2026-1699?

CVE-2026-1699 is rated Critical with a CVSS score of 10.0. 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-1699?

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

What does CVE-2026-1699 affect?

CVE-2026-1699 affects Eclipse Theia GitHub Actions workflow, GitHub Actions CI environment, Theia website repository. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-1699?

Disable pull_request_target; rotate secrets; audit repos

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

executive summary
technical analysis
affected
Eclipse Theia GitHub Actions workflowGitHub Actions CI environmentTheia website repository
impact

Arbitrary code execution in CI via untrusted PRs; exfiltrate secrets, publish malicious packages, modify website.

action required

Immediate action required

affected versions
Eclipse Foundation Eclipse Theia - Website
  • affected< 2fb0cc4bfc372cfaef79feb4eebb6563778b2560

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