High-Severity Flaw in Amazon Q Developer Leads to AWS Credential Theft via Malicious Repositories

A severe security vulnerability, tracked as CVE-2026-12957, has been identified in Amazon Q Developer, Amazon's AI-powered coding assistant. This flaw presents a critical risk, enabling attackers to steal AWS cloud credentials simply by tricking a developer into opening a specially crafted, malicious code repository. The exploit requires no further interaction from the developer beyond opening the project, making it particularly dangerous. The core of the issue lies in what is described as an "MCP trust gap" within the Amazon Q Developer plugin. A single, maliciously configured file within a repository can trigger the exfiltration of active AWS session tokens to an attacker-controlled server. This direct access to credentials could lead to widespread compromise of AWS accounts, potentially exposing production data, infrastructure, and other sensitive resources. Organizations whose developers utilize Amazon Q Developer are facing an immediate and direct threat of AWS account compromise. The vulnerability was publicly disclosed on June 26, 2026, following Amazon's release of a patch on May 12, 2026. This proactive patching by Amazon aimed to address the issue before widespread exploitation. To safeguard against this threat, all developers using affected versions of the Amazon Q Developer plugin (specifically VS Code plugin ≥2.20, JetBrains ≥4.3, Eclipse ≥2.7.4) are urged to apply the vendor-provided patch immediately. Furthermore, it is critical that all AWS credentials associated with these developer environments be rotated within 48 hours of applying the patch. Failure to do so leaves organizations vulnerable to attackers who might have already compromised credentials. Security teams are also advised to monitor AWS CloudTrail and GuardDuty findings for at least 30 days post-remediation, specifically looking for suspicious `AssumeRole` calls originating from unfamiliar IP addresses or geographic regions. This monitoring helps detect if attackers managed to retain copies of stolen STS tokens or establish persistent backdoors. The vulnerability highlights the ongoing challenges in securing developer tooling and the importance of supply chain security in modern cloud environments.