CVE-2026-46580
CVE-2026-46580 is a CWE-829 vulnerability in @theia/ai-chat-ui. O3 Security confirms whether CVE-2026-46580 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
[Eclipse Theia] Indirect Prompt Injection via Auto-Loaded Workspace Prompt Template Files in AI Chat
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@theia/ai-chat-uinpm@theia/ai-chatnpm@theia/ai-claude-codenpmDescription
In Eclipse Theia versions prior to 1.71.0, files matching the pattern .prompts/*.prompttemplate in a workspace were automatically loaded and could override or extend the AI agent's system prompts. An attacker could craft a malicious repository containing prompt template files that, when the workspace was opened in Theia, replaced the AI's system instructions with attacker-controlled content (indirect prompt injection). Combined with other AI chat features available in untrusted workspaces, this enabled attack chains leading to data exfiltration via Markdown image rendering or arbitrary command execution via task definitions.
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 CVE-2026-46580 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 CVE-2026-46580 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 CVE-2026-46580. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-46580 in your dependencies?
O3 detects CVE-2026-46580 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.