CVE-2025-8217

MEDIUMPre-NVD 4.04.0
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.0 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.0
EG Score
4.0(medium)
EPSS
9.6%
KEV
Not listed

Published

July 30, 2025

Last Modified

June 17, 2026

Vendor Advisories for CVE-2025-8217(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 23:22 UTCEPSS rescore
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-27 03:08 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-24 14:04 UTCEPSS rescore
  21. 2026-06-23 21:32 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
Show 63 more
  1. 2026-06-21 01:59 UTCEPSS rescore
  2. 2026-06-21 01:59 UTCEPSS rescore
  3. 2026-06-19 19:25 UTCEPSS rescore
  4. 2026-06-19 19:25 UTCEPSS rescore
  5. 2026-06-18 17:52 UTCEPSS rescore
  6. 2026-06-18 17:52 UTCEPSS rescore
  7. 2026-06-17 17:53 UTCEPSS rescore
  8. 2026-06-16 17:52 UTCEPSS rescore
  9. 2026-06-15 17:48 UTCEPSS rescore
  10. 2026-06-14 23:18 UTCEPSS rescore
  11. 2026-06-13 23:00 UTCEPSS rescore
  12. 2026-06-13 23:00 UTCEPSS rescore
  13. 2026-06-12 23:12 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-11 14:00 UTCEPSS rescore
  16. 2026-06-10 22:18 UTCEPSS rescore
  17. 2026-06-10 13:22 UTCEPSS rescore
  18. 2026-06-08 14:17 UTCEPSS rescore
  19. 2026-06-08 14:17 UTCEPSS rescore
  20. 2026-06-07 15:24 UTCEPSS rescore
  21. 2026-06-07 15:24 UTCEPSS rescore
  22. 2026-06-06 13:47 UTCEPSS rescore
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-05 22:47 UTCEPSS rescore
  25. 2026-06-05 22:46 UTCEPSS rescore
  26. 2026-06-05 06:10 UTCEPSS rescore
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-04 13:12 UTCEPSS rescore
  29. 2026-06-04 13:12 UTCEPSS rescore
  30. 2026-06-02 20:13 UTCEPSS rescore
  31. 2026-06-01 13:51 UTCEPSS rescore
  32. 2026-06-01 13:51 UTCEPSS rescore
  33. 2026-05-31 22:30 UTCEPSS rescore
  34. 2026-05-31 22:30 UTCEPSS rescore
  35. 2026-05-31 00:16 UTCEPSS rescore
  36. 2026-05-31 00:16 UTCEPSS rescore
  37. 2026-05-29 13:44 UTCEPSS rescore
  38. 2026-05-29 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-28 13:44 UTCEPSS rescore
  41. 2026-05-28 13:44 UTCEPSS rescore
  42. 2026-05-27 13:40 UTCEPSS rescore
  43. 2026-05-27 13:40 UTCEPSS rescore
  44. 2026-05-27 13:40 UTCEPSS rescore
  45. 2026-05-27 13:40 UTCEPSS rescore
  46. 2026-05-26 13:44 UTCEPSS rescore
  47. 2026-05-26 13:44 UTCEPSS rescore
  48. 2026-05-26 13:44 UTCEPSS rescore
  49. 2026-05-26 07:18 UTCEPSS rescore
  50. 2026-05-26 07:18 UTCEPSS rescore
  51. 2026-05-26 07:18 UTCEPSS rescore
  52. 2026-05-23 00:09 UTCEG score recompute
  53. 2026-05-22 21:16 UTCEPSS rescore
  54. 2026-05-22 21:16 UTCEPSS rescore
  55. 2026-05-21 22:43 UTCEPSS rescore
  56. 2026-05-21 10:33 UTCEG score recompute
  57. 2026-05-20 22:37 UTCEPSS rescore
  58. 2026-05-20 22:37 UTCEPSS rescore
  59. 2026-05-20 22:37 UTCEPSS rescore
  60. 2026-05-20 11:21 UTCEPSS rescore
  61. 2026-05-20 11:21 UTCEPSS rescore
  62. 2026-05-20 11:21 UTCEPSS rescore
  63. 2026-05-18 21:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-8217?
CVE-2025-8217 is a medium vulnerability published on July 30, 2025. 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…
When was CVE-2025-8217 disclosed?
CVE-2025-8217 was first published in the National Vulnerability Database on July 30, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-8217 actively exploited?
CVE-2025-8217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-8217?
CVE-2025-8217 has a CVSS v3 base score of 4.0 (NVD).
How do I remediate CVE-2025-8217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-8217, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-8217

Explore →

Is Your Infrastructure Affected by CVE-2025-8217?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.