An awslabs/mcp security advisory published on 2 November 2026 says AWS Serverless MCP Server version 0.2.1 addresses a path traversal vulnerability in its deployment status component. The advisory lists versions below 0.2.1 of the pip package awslabs.aws-serverless-mcp-server as affected and identifies the issue as CVE-2026-116635, rated Moderate with a CVSS score of 6.1.[1]

According to the advisory, an actor able to influence the MCP agent could supply directory traversal sequences or an absolute path through the project name input. Under the described conditions, this could let the agent read JSON files outside the intended deployment status directory, returning their contents to the agent’s context. If the server was started with --enable-write, the issue could also allow JSON files outside that directory to be created or overwritten. The advisory says overwritten data would consist of serverless deployment metadata.[1]

The maintainers recommend upgrading to the latest version and incorporating the fixes into forked or derivative code. They list 0.2.1 as the patched version and state that there is no workaround. These are the advisory’s remediation claims; reading the notice does not independently establish the patch’s behavior.[1]

[1]: https://github.com/awslabs/mcp/security/advisories/GHSA-r6mm-377j-qg8m

Sources

  1. Improper limitation of a pathname to a restricted directory in the AWS Serverless MCP Servergithub.com · 2 Nov 2026

Check or correct this page

Verification record

The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.

1fd1356c542a030ab239d9e0b1e9845ee4d8d333c767409ad165462121a9036d