GHSA-qwjm-9c66-w4q4
[Eclipse Theia] Data Exfiltration via Markdown Image Rendering in AI Chat
Blast Radius
@theia/ai-chat-ui📦@theia/ai-chat📦@theia/ai-claude-code📦@theia/ai-code-completion📦@theia/ai-core📦@theia/ai-editor📦@theia/ai-ideReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
In Eclipse Theia versions prior to 1.71.0, the AI chat rendered Markdown image tags from AI responses, triggering HTTP requests to arbitrary external URLs without restriction. Combined with prompt injection in a malicious workspace, an attacker could induce the AI agent to construct image URLs encoding sensitive information from the workspace or conversation context, exfiltrating it to attacker-controlled servers. The workspace trust enforcement introduced in v1.71.0 mitigates the documented attack chain by disabling AI features in untrusted workspaces.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @theia/ai-chat-ui | all versions | 1.71.0 |
| 📦npm | @theia/ai-chat | all versions | 1.71.0 |
| 📦npm | @theia/ai-claude-code | all versions | 1.71.0 |
| 📦npm | @theia/ai-code-completion | all versions | 1.71.0 |
| 📦npm | @theia/ai-core | all versions | 1.71.0 |
| 📦npm | @theia/ai-editor | all versions | 1.71.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @theia/ai-chat-ui. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @theia/ai-chat-ui to 1.71.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwjm-9c66-w4q4 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 pinpoints whether GHSA-qwjm-9c66-w4q4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-qwjm-9c66-w4q4. 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-qwjm-9c66-w4q4 in your dependencies?
O3 detects GHSA-qwjm-9c66-w4q4 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.