GHSA-g9jw-92q7-g7fj — @theia/debug
Fix: eclipse-theia/theia#16917GHSA-g9jw-92q7-g7fj is a CWE-829 vulnerability in @theia/debug. A fix is available for @theia/debug — see the affected versions and patch details below.
[Eclipse Theia] Arbitrary Command Execution via Untrusted Workspace Task Definitions
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-g9jw-92q7-g7fj.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@theia/debugnpm@theia/tasknpm@theia/workspacenpmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @theia/debug | all versions | 1.69.0npm install @theia/debug@1.69.0 |
| 📦npm | @theia/task | all versions | 1.69.0npm install @theia/task@1.69.0 |
| 📦npm | @theia/workspace | all versions | 1.69.0npm install @theia/workspace@1.69.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @theia/debug, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @theia/debug to 1.69.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g9jw-92q7-g7fj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g9jw-92q7-g7fj can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g9jw-92q7-g7fj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g9jw-92q7-g7fj in your dependencies?
O3 Security finds GHSA-g9jw-92q7-g7fj across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.