# CVE-2025-8217: Inert Malicious script injected into Amazon Q Developer Visual Studio Code (VS Code) Extension

> Attackers could inject malicious code into the Amazon Q Developer VS Code extension, though execution was blocked by a syntax error.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-7g7f-ff96-5gcw

## What is CVE-2025-8217?

CVE-2025-8217 is a medium-severity code injection vulnerability in Amazon Q Developer VS Code Extension, published on 30 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Amazon Q Developer Visual Studio Code (VS Code) extension v1.84.0 contains inert, injected code designed to call the Q Developer CLI. The code executes when the extension is launched within the VS Code environment; however the injected code contains a syntax error which prevents it from making a successful API call to the Q Developer CLI.

To mitigate this issue, users should upgrade to version v1.85.0. All installations of v1.84.0 should be removed from use.

Weakness: CWE-506 (Embedded Malicious Code)

## Which versions are affected by CVE-2025-8217?


## How do I fix CVE-2025-8217?

No fix has been published for CVE-2025-8217 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8217 being exploited?

There is no known exploitation of CVE-2025-8217 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-8217 and fix it if it is affected.

What it is: CVE-2025-8217 is a medium-severity code injection vulnerability in Amazon Q Developer VS Code Extension, published on 30 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8217 in the wild and no public exploit code.

Affected product: Amazon Q Developer VS Code Extension. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-8217/ (Markdown: https://insights.sbomify.com/CVE-2025-8217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-8217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-8217
- OSV: https://osv.dev/vulnerability/CVE-2025-8217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-8217/
Summaries are generated and may contain mistakes; the official description above is the record.