How severe is GHSA-3jww-hxqj-wfq2?

No CVSS score has been assigned to GHSA-3jww-hxqj-wfq2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3jww-hxqj-wfq2?

GHSA-3jww-hxqj-wfq2 affects the following packages: @theia/ai-chat-ui (npm), @theia/ai-chat (npm), @theia/ai-claude-code (npm), @theia/ai-code-completion (npm), @theia/ai-core (npm), @theia/ai-editor (npm), @theia/ai-ide (npm). Ecosystems affected: npm.

How do I fix GHSA-3jww-hxqj-wfq2?

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-3jww-hxqj-wfq2 is resolved across your whole dependency graph.

How do I detect GHSA-3jww-hxqj-wfq2 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @theia/ai-chat-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3jww-hxqj-wfq2 if there is no patch (or I can't update yet)?

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.

Is GHSA-3jww-hxqj-wfq2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3jww-hxqj-wfq2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-3jww-hxqj-wfq2?

GHSA-3jww-hxqj-wfq2 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-3jww-hxqj-wfq2?

GHSA-3jww-hxqj-wfq2 is classified as CWE-829 (CWE-829). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-3jww-hxqj-wfq2 published, and has it been updated?

GHSA-3jww-hxqj-wfq2 was published on June 18, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

[Eclipse Theia] Indirect Prompt Injection via Adversarial…

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-3jww-hxqj-wfq2.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

7 pkgs affected

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.

7other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@theia/ai-chat-uinpm

10Kdownloads / week

@theia/ai-chatnpm

10Kdownloads / week

@theia/ai-claude-codenpm

3Kdownloads / week

Description

In Eclipse Theia versions prior to 1.71.0, the AI chat agent processed workspace file and directory names as part of its prompt context without distinguishing them from system instructions. An attacker could craft a malicious repository with adversarial directory or file names that, when analyzed by the AI agent, would cause the agent to follow attacker-controlled instructions (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

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@theia/ai-chat-ui`	all versions	1.71.0`npm install @theia/ai-chat-ui@1.71.0`
📦npm	`@theia/ai-chat`	all versions	1.71.0`npm install @theia/ai-chat@1.71.0`
📦npm	`@theia/ai-claude-code`	all versions	1.71.0`npm install @theia/ai-claude-code@1.71.0`
📦npm	`@theia/ai-code-completion`	all versions	1.71.0`npm install @theia/ai-code-completion@1.71.0`
📦npm	`@theia/ai-core`	all versions	1.71.0`npm install @theia/ai-core@1.71.0`
📦npm	`@theia/ai-editor`	all versions	1.71.0`npm install @theia/ai-editor@1.71.0`

Affected Products

1 product · 1 configurations

Application

theiaeclipse

< 1.71.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @theia/ai-chat-ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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-3jww-hxqj-wfq2 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.

Frequently Asked Questions

In Eclipse Theia versions prior to 1.71.0, the AI chat agent processed workspace file and directory names as part of its prompt context without distinguishing them from system instructions. An attacker could craft a malicious repository with adversarial directory or file names that, when analyzed by the AI agent, would cause the agent to follow attacker-controlled instructions (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

O3 Security · Impact-Aware SCA

Is GHSA-3jww-hxqj-wfq2 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works

[Eclipse Theia] Indirect Prompt Injection via Adversarial Workspace File and Directory Names in AI ChatGHSA-3jww-hxqj-wfq2