CVE-2026-116635: Improper limitation of a pathname to a restricted directory in the deployment status component of the AWS Serverless MCP Server
Source AWS Security Bulletins
Not known to be exploited · CVSS 6.1 Medium : upgrade to 0.2.1 when convenient.
Data as of 3 Nov 2026, 00:43 UTC
Thin evidence
One scorer or none| CNA (AMZN) | CVSS 3.1 | 6.1 |
|---|---|---|
| CNA (AMZN) | CVSS 4.0 | 6.9 |
- Patch
- Available – fixed in 0.2.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade aws-serverless-mcp-server and awslabs-aws-serverless-mcp-server to 0.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWSaws-serverless-mcp-server | Affected
| Fixed in
|
PyPIawslabs-aws-serverless-mcp-serverpkg:pypi/awslabs-aws-serverless-mcp-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to version 0.2.1 or later of the awslabs.aws-serverless-mcp-server where this vulnerability is fixed. No other mitigation guidance is provided in the bulletin.
Description
CVE-2026-116635 is a vulnerability in the deployment status component of the AWS Serverless MCP Server prior to version 0.2.1. It involves improper limitation of pathnames, which may allow an attacker who can influence the MCP agent to read JSON files outside the intended directory. If write access is enabled, the attacker could also create or overwrite JSON files outside the deployment status directory.