Amazon Q Developer at a glance
AWS bulletin 2026-047-AWS covers CVE-2026-12957 and CVE-2026-12958 in Language Servers for AWS, used by the Amazon Q Developer IDE plugins. A crafted, trusted workspace could auto-run commands from project config files or write through a symlink outside the workspace. Fixed in 1.69.0.
Amazon Q Developer: status
- Affected
- Language Servers for AWS before 1.69.0 (CVE-2026-12957 fixed in 1.65.0)
- Amazon Q Developer for Visual Studio Code before 2.20
- Amazon Q Developer for JetBrains before 4.3
- Amazon Q Developer for Eclipse before 2.7.4
- AWS Toolkit with Amazon Q for Visual Studio before 1.94.0.0
- Status as of
- Discovered by
- Wiz and Maor Dokhanian
What changed with Amazon Q Developer
AWS published security bulletin 2026-047-AWS on June 23, 2026, for two flaws in Language Servers for AWS, the component behind the Amazon Q Developer plugins. CVE-2026-12957 is a trust-boundary issue: after a user opens a crafted workspace and accepts the trust prompt, commands in project configuration files could run automatically. CVE-2026-12958 is missing symlink validation: a link in the workspace could send the agent's later file writes to a path outside it, without asking for approval.
AWS rates both High (CVSS v4 8.5). Language Servers for AWS 1.69.0 fixes both; the first was already fixed in 1.65.0. The affected plugins are Amazon Q Developer for VS Code before 2.20, for JetBrains before 4.3, for Eclipse before 2.7.4, and AWS Toolkit with Amazon Q for Visual Studio before 1.94.0.0. AWS says there are no workarounds and credits Wiz and Maor Dokhanian.
How to fix it: Amazon Q Developer
1. Update
Upgrade to the latest Amazon Q Developer IDE plugin, which bundles Language Servers for AWS 1.69.0 or later. AWS lists no workarounds.
aws.amazon.com (opens in a new tab)2. Update
If you maintain forked or derivative code of the language servers, make sure it includes both fixes.
aws.amazon.com (opens in a new tab)
Advisories
- AWS Security Bulletin 2026-047-AWS (opens in a new tab)aws.amazon.com
- GHSA-xhcr-j4j9-3gh7 (CVE-2026-12957) (opens in a new tab)github.com
- GHSA-6v3r-4p5c-mrp5 (CVE-2026-12958) (opens in a new tab)github.com
- NVD CVE-2026-12957 (opens in a new tab)nvd.nist.gov
- NVD CVE-2026-12958 (opens in a new tab)nvd.nist.gov
Where to compare Amazon Q Developer
Independent leaderboards and official resources for comparing this model yourself. Rankings change often; each site shows its own current data.
Why Amazon Q Developer matters for businesses
Opening someone else's repository and clicking trust is routine for developers, and here it was enough to hand an AI assistant's tools to an attacker. Update every Amazon Q Developer plugin, make sure forks or internal builds of the language servers include the fixes, and treat the workspace trust prompt as a real security decision rather than a formality.
Sources for this story
- CVE-2026-12957 and CVE-2026-12958, Issues in Language Servers for AWS and Amazon Q Developer Plugins (opens in a new tab)Official
AWS Security Bulletins · aws.amazon.com
- Arbitrary Code Execution in Language Servers for AWS (GHSA-xhcr-j4j9-3gh7) (opens in a new tab)Official
AWS on GitHub · github.com
- Arbitrary file write in Language Servers for AWS (GHSA-6v3r-4p5c-mrp5) (opens in a new tab)Official
AWS on GitHub · github.com
- CVE-2026-12957 Detail (opens in a new tab)Official
NIST National Vulnerability Database · nvd.nist.gov
- CVE-2026-12958 Detail (opens in a new tab)Official
NIST National Vulnerability Database · nvd.nist.gov
Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.
- #security
- #cve
- #ai-coding-agents
- #workspace-trust
- #amazon-q-developer
- #aws