Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44691 high CVSS 8.8

Vulnerability in @theia/debug (CVE-2026-44691)

Summary

Vulnerability in @theia/debug (CVE-2026-44691). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.69.0 or later.

Original description

The description as published by the source.

In Eclipse Theia versions prior to 1.69.0, custom task definitions in workspace files (e.g. .theia/tasks.json, .vscode/tasks.json) could be executed without requiring workspace trust. An attacker could craft a malicious repository that, when cloned and opened in Theia, leads to execution of arbitrary commands with the user's privileges. In combination with AI chat features and a workspace .theia/settings.json that disabled tool confirmation, this could be triggered automatically by sending a message in the AI chat.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44691 has been found in @theia/debug.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade @theia/debug to 1.69.0 or later.
If unsure, ask your IT team or search "@theia/debug CVE-2026-44691" on the vendor's site.

CVE-2026-44691 (@theia/debug) — CWE-829 / CVSS v3 8.8
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.69.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-829) exists in @theia/debug.

📍 Affected scope

Check the vendor advisory for the affected versions of @theia/debug.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.69.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@theia/debug' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@theia/debug' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @theia/debug を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @theia/debug to 1.69.0

    ステージング環境で 1.69.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @theia/debug
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.69.0"}]}]
npm @theia/task
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.69.0"}]}]
npm @theia/workspace
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.69.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details