CVE-2026-85654 - Code injection in the CDK generator in Amazon awslabs.dynamodb-mcp-server
AWS Security Bulletins has published a new security advisory. Here is a summary and what to do.
Key points
- New advisory from AWS Security Bulletins.
- Review affected versions in the advisory.
- Apply updates promptly.
AWS Security Bulletins published a security advisory titled “CVE-2026-85654 - Code injection in the CDK generator in Amazon awslabs.dynamodb-mcp-server”.
At a glance
- Publisher
- AWS Security Bulletins
- CVEs
- CVE-2026-85654
What the advisory says
Bulletin ID: 2026-097-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 09/04/2026 10:00 AM PDT Description: Amazon awslabs.dynamodb-mcp-server is an open-source Model Context Protocol (MCP) server that enables AI coding assistants to interact with Amazon DynamoDB, including table design, data modeling, and CDK infrastructure generation. We identified CVE-2026-85654, an improper neutralization of special elements used in a template engine in the CDK generator component. Under certain circumstances, a context-dependent actor could execute arbitrary code on the host that deploys the generated application via crafted table, index, or attribute names in a data model file. Impacted versions: >= 2.0.10 AND <= 2.1.5 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
What should you do?
- Read the full vendor advisory linked below and confirm whether you run affected versions.
- Schedule the recommended update, prioritising internet-facing systems.
- Watch for exploitation reports; unpatched edge devices are frequent targets.
What to do and how to stay safe: CVE-2026-85654
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
