NewsAgency

CVE-2026-12957 and CVE-2026-12958 - Issues in Language Servers for AWS and Amazon Q Developer Plugins

2 dakika okuma süresi

CVE-2026-12957 and CVE-2026-12958 - Issues in Language Servers for AWS and Amazon Q Developer Plugins

Bulletin ID: 2026-047-AWS | Publication Date: 06/23/2026 09:00 AM PDT

Language Servers for AWS provide the underlying language-server runtime that powers Amazon Q Developer’s AI coding assistance across its IDE plugins (Visual Studio Code, JetBrains, Eclipse, and Visual Studio).

CVE-2026-12957

An improper trust boundary enforcement issue in Language Servers for AWS before version 1.65.0. If a local user opens a maliciously crafted workspace, any commands within the project configuration files may be automatically executed. This issue requires the user to trust the workspace when prompted.

Wiz Research discovered that Amazon Q automatically loaded MCP server configurations from .amazonq/mcp.json within the workspace — no prompt, no consent, no workspace trust check. Combined with full environment inheritance, this enabled immediate code execution and cloud credential theft when a developer opened a malicious repository.

Amazon fixed the vulnerability by requiring explicit user approval before any MCP server can start, and by restricting the environment variables that MCP servers can access.

CVE-2026-12958

A missing symlink-validation issue in Language Servers for AWS before version 1.69.0. This may occur when a local user opens a workspace with a maliciously crafted symlink that resolves to a file path outside the workspace trust boundary.

Both issues are remediated in Language Servers for AWS version 1.69.0.

Affected products & versions

  • Language Servers for AWS: < 1.69.0
  • Amazon Q Developer for Visual Studio Code: < 2.20
  • Amazon Q Developer for JetBrains: < 4.3
  • Amazon Q Developer for Eclipse: < 2.7.4
  • AWS Toolkit with Amazon Q for Visual Studio: < 1.94.0.0

Resolution

Upgrade to the latest Amazon Q Developer IDE plugin bundling Language Servers for AWS 1.69.0. No workarounds available.

Acknowledgement: Amazon thanked Wiz for collaborating through coordinated vulnerability disclosure. Wiz reported the issue April 20, 2026; initial fix deployed May 12, 2026; public disclosure June 23–26, 2026.

A minimal proof-of-concept showed that a single malicious .amazonq/mcp.json file could exfiltrate active AWS session credentials to an attacker-controlled server — no clicks, no prompts, no warning.

Affected IDEs: VS Code, JetBrains, Eclipse, Visual Studio.

Grafik Görünümü