CVE-2026-116635: AWS Serverless MCP Server lets a crafted project name read or overwrite JSON files outside its directory (fixed 0.2.1)
The deployment-status component of awslabs.aws-serverless-mcp-server before 0.2.1 built file paths from the serverless project name without limiting them to its directory. Anyone who can influence the agent's project name (for example through prompt injection) could make it read any JSON file the server can reach and, with --enable-write, create or overwrite JSON files elsewhere. Fixed in 0.2.1. Separately, AWS fixed a run_script validator bypass in its hosted AWS MCP Server (CVE-2026-115845) service-side.
What it is
Relative (../) or absolute paths in the project name input were used as-is for the deployment status file (CWE-23 / CWE-36).
Read: a JSON file outside the intended directory is returned into the agent's context. Write (only with --enable-write): an existing JSON file is clobbered with deployment metadata.
awslabs/mcp advisory GHSA-r6mm-377j-qg8m (2 Nov 2026) lists < 0.2.1 as affected and 0.2.1 as patched; AWS says there is no workaround.
Related, no action needed: AWS security bulletin 2026-149-AWS (23 Oct 2026) says an incomplete deny list in the Python validator of the hosted AWS MCP Server's run_script tool could let an authenticated user run arbitrary code inside their own isolated session (CVE-2026-115845). AWS fixed it on the service side.
How to check
- Find the version you run: `pip show awslabs.aws-serverless-mcp-server`, or the version pinned in your MCP client's uvx launch line.
- Check whether your MCP config starts it with --enable-write.
How to fix
- Upgrade to awslabs.aws-serverless-mcp-server 0.2.1 or later (pin it in the uvx line, e.g. [email protected]).
- Only enable --enable-write when you need it, and treat project names coming from documents or other untrusted content with care.
pip show awslabs.aws-serverless-mcp-server | grep -i ^version
grep -rn 'aws-serverless-mcp-server' ~/.cursor/mcp.json ~/.aws/amazonq/mcp.json ~/Library/Application\ Support/Claude/claude_desktop_config.json 2>/dev/null Sources
- criticalMalicious npm package @guicai777/mcp-doctor posed as an MCP diagnostic tool and dropped a hidden Windows executable, with a README telling users to run mshta (MAL-2026-20295)
- criticalCVE-2026-77359: Jupyter MCP Server's /api/connect and /api/stop routes skipped the token and Origin checks, so a website or network caller could repoint it to an attacker's Jupyter backend (fixed 1.0.3)
- criticalMalicious npm packages posing as AI SDKs and MCP servers: character-ai-sdk, char-ai-sdk, @mibbp/agent-observer, mrnima-openai-chatgpt-bot and @fdcasj_dfew/md-doc-mcp
- criticalCVE-2026-76807: Doist's official Todoist MCP HTTP server let any website use DNS rebinding to read, create and delete your Todoist data (fixed 10.3.3)