Amazon Q Developer Flaw Let Malicious Repos Execute Code and Steal Cloud Credentials
Amazon patched a high-severity flaw in Amazon Q Developer and the underlying Language Servers for AWS that allowed a booby-trapped repository to execute attacker-controlled commands when a developer opened and trusted a workspace. Tracked as CVE-2026-12957 and rated CVSS 8.5, the issue involved unsafe handling of Model Context Protocol (MCP) configuration files such as .amazonq/mcp.json, which could cause Amazon Q integrations for VS Code, JetBrains, Eclipse, and Visual Studio to launch local processes defined by an attacker. Those processes inherited the developer’s environment, exposing AWS credentials, API keys, authentication tokens, and SSH agent access already present on the machine.
Wiz Research reported the vulnerability to AWS on April 20, and AWS fixed it on May 12, later publishing an advisory and releasing remediation in Language Servers for AWS 1.65.0. AWS also addressed a related flaw, CVE-2026-12958, involving missing symlink validation that could enable arbitrary file writes outside the workspace trust boundary; customers were advised to upgrade to version 1.69.0 to cover both issues. Researchers said likely attack paths include fake coding tests, typosquatted open-source packages, and malicious pull requests, while noting the weakness reflects broader trust-boundary problems emerging across AI coding assistants that adopt MCP-style workspace configuration.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Wiz publicly discloses Amazon Q repository attack flaw
Wiz published its write-up describing how a malicious repository containing a .amazonq/mcp.json file could trigger local process execution in Amazon Q Developer and expose AWS credentials, API keys, tokens, and SSH agent access. Reports said no known public exploitation had been observed.
CVE-2026-12958 is publicly published
The arbitrary file write vulnerability CVE-2026-12958 was published publicly, with remediation guidance to upgrade Language Servers for AWS to version 1.69.0 or later.
AWS publishes advisory for CVE-2026-12957 and CVE-2026-12958
AWS published a security bulletin covering CVE-2026-12957 and the related symlink-handling flaw CVE-2026-12958 affecting Language Servers for AWS and Amazon Q Developer plugins.
AWS fixes CVE-2026-12957 in Language Servers for AWS 1.65.0
Amazon remediated CVE-2026-12957 on May 12, with the fix delivered in Language Servers for AWS version 1.65.0 and propagated to Amazon Q Developer integrations across supported IDEs.
Wiz reports Amazon Q command-execution flaw to AWS
Wiz Research notified AWS about CVE-2026-12957, a high-severity flaw in Amazon Q Developer and Language Servers for AWS that could let a malicious repository execute attacker-controlled commands and expose developer credentials.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
12 references tracked. Mallory keeps watching after this page renders.
Amazon Q VS Extension Flaw Leads to Cloud Credential Theft
darkreading.com
Open sourceAmazon Q Developer extension vulnerability could have exposed cloud credentials | brief | SC Media
scworld.com
Open sourceAmazon Q Vulnerability Let Attackers Execute Code and Access Sensitive Cloud Environments
cybersecuritynews.com
Open sourceAmazon Q Flaw Enabled Cloud Credential Theft via Malicious Repositories - SecurityWeek
securityweek.com
Open sourceCVE-2026-12958 - Arbitrary file write in Language Servers for AWS
cvefeed.io
Open sourceCVE-2026-12957 - Arbitrary Code Execution in Language Servers for AWS
cvefeed.io
Open sourceCVE-2026-12957 and CVE-2026-12958 - Issues in Language Servers for AWS and Amazon Q Developer Plugins
aws.amazon.com
Open sourceArbitrary Code Execution in Language Servers for AWS · Advisory · aws/language-servers · GitHub
github.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


