Security Digest · Vulnerability record

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

The Amazon Q Developer Visual Studio Code (VS Code) extension v1.84.0 contains inert, injected code designed to call the Q Developer CLI.

CVSS 5.1 Medium EPSS 0.2% · p12 Most can relax

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.2%, percentile 12: FIRST’s model estimates a 0.2% chance of exploitation activity in the next 30 days, higher than 12% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Needs local access needed. Lower urgency for most teams unless an attacker could already run code on the machine.
  • Editorial verdict: Most can relax. Amazon Q VS Code Extension 1.84.0 Shipped a Wiper Prompt — A real supply-chain compromise with a payload that AWS says could not run; if nothing in your fleet still has 1.84.0, there is nothing left to do.

What it is

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 type: CWE-506.

Product: Amazon Q Developer VS Code Extension · Assigned by: AMZN · Published: 2025-07-30

Affected and fixed versions

VendorProductAffected versions (per CVE record)
AmazonQ Developer VS Code Extension1.84.0 < 1.85.0, sha256:47f7840ecab6312d2733e1274c513050405886c70f2037fb2f1e9099872b0464

Severity scores

Scored byCVSSScoreVector
AMZN4.05.1 MediumCVSS: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
AMZN3.14 MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
  • Attack vector: local access needed
  • Attack complexity: low
  • Attack requirements: none
  • Privileges required: none (no login)
  • User interaction: none

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable no, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.22% probability of exploitation activity in the next 30 days; percentile 12.

Timeline

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vendor and project advisories, patches

  1. aws.amazon.com aws.amazon.com
  2. github.com github.com

Vulnerability records

  1. CVE.org record CVE-2025-8217 cve.org
  2. NVD entry CVE-2025-8217 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com

Today’s Security Digest