Amazon Q Developer Vulnerability Allows Cloud Credential Theft via Malicious Repositories

iconCryptoBriefing
Share
AI summary iconSummary
Vulnerability news emerged as Wiz Research disclosed a flaw in Amazon Q Developer, tracked as CVE-2026-12957. The issue allowed automatic execution of MCP server configurations, exposing AWS credentials. Amazon released a protocol update on May 12, 2026, with full disclosure following on June 26. Developers are urged to upgrade to version 1.69.0, which also fixes CVE-2026-12958.

A vulnerability in Amazon’s AI-powered coding assistant, Amazon Q Developer, allowed attackers to steal cloud credentials simply by tricking a developer into opening a poisoned code repository. The flaw, tracked as CVE-2026-12957, carries a CVSS score of 8.5 out of 10.

Wiz Research, the security firm that discovered the bug, found that the Amazon Q Developer extension for IDEs like Visual Studio Code would automatically load and execute Model Context Protocol (MCP) server configurations without asking the developer’s permission first. Open a malicious repo, and hidden commands run silently in the background with full access to your environment variables, including your AWS credentials.

How the attack works

The exploit is elegant in its simplicity. An attacker places a single .amazonq/mcp.json file inside a code repository. When an unsuspecting developer clones and opens that repo in their IDE with the Amazon Q Developer extension installed, the MCP configuration file runs automatically.

Advertisement

Those commands don’t run in some sandboxed environment. They inherit the developer’s complete set of environment variables. For anyone working with AWS, that typically includes access keys, session tokens, and region configurations. The result is silent data exfiltration with no pop-up warnings, no permission dialogs, and no indication that anything happened at all.

Timeline and patch details

Wiz reported the vulnerability to Amazon on April 20, 2026. Amazon released an initial patch on May 12, 2026, in Language Servers for AWS version 1.65.0. Public disclosure followed on June 26, 2026, giving organizations roughly six weeks to update before the details went public.

Amazon has recommended that users upgrade to version 1.69.0 for more comprehensive protection. That later version also addresses a related vulnerability, CVE-2026-12958, which involves symlink validation issues in MCP configurations.

No instances of public exploitation have been recorded so far.

A pattern, not an isolated incident

Similar flaws have been reported around the same time for other AI coding tools, including Claude Code, Cursor, and Windsurf. The common thread is MCP, the Model Context Protocol that AI coding assistants use to connect with external tools and data sources. When an AI coding tool automatically loads configuration files from a repository, it implicitly trusts whatever the repository author put there.

For developers and organizations using AWS, the immediate action is straightforward: update your Amazon Q Developer extension to at least version 1.65.0, ideally version 1.69.0. Organizations running cloud workloads should also audit whether any of their developers may have opened unfamiliar repositories while the vulnerable extension was active. Rotating AWS credentials as a precaution is advisable given that the exploit leaves no visible trace.

The CVSS score of 8.5 puts this squarely in the “high severity” category. For context, a score above 9.0 is considered critical, and anything above 7.0 demands prompt attention.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.