Improper limitation of a pathname to a restricted directory in the deployment status component of the AWS Serverless MCP Server
Affects AWS Serverless MCP Server before 0.2.1 when a serverless project name contains a path; writes also need the --enable-write flag. Fixed in 0.2.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.2.1
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Attacker supplies a serverless project name containing a relative path (directory traversal sequences) or an absolute path. For reads, the path must end in a valid JSON file. For writes, the --enable-write flag must be used.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 11/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The AWS Serverless MCP Server (aws-serverless-mcp-server), used with AI agents for deploying serverless applications, is affected by a path traversal flaw in its deployment status component. An attacker who can influence the agent's input could potentially read JSON files outside the intended directory, or create or overwrite such files where write access is enabled.
Read the original description
Improper limitation of a pathname to a restricted directory in the deployment status component of the AWS Serverless MCP Server (aws-serverless-mcp-server) before v0.2.1 might allow an actor who can influence the MCP agent to read the contents of JSON files outside the intended deployment status directory. Where write access has been enabled, to create or overwrite JSON files outside that directory. This issue is reachable through directory traversal sequences or an absolute path supplied in the project name input. To remediate this issue, users should upgrade to version v0.2.1.
What to do
Check whether your setup matches what the bug needs.
Attacker supplies a serverless project name containing a relative path (directory traversal sequences) or an absolute path. For reads, the path must end in a valid JSON file. For writes, the --enable-write flag must be used.Upgrade to a fixed version: 0.2.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- AWS aws-serverless-mcp-server
fixed in 0.2.1
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116635
What does this mean?
A serverless project name that contains a relative or absolute path is not kept inside the deployment status directory. An attacker who can influence the MCP agent can read JSON files outside that directory, and with write enabled can create or overwrite JSON files there.Source: github.com
Am I affected, and how do I check?
Versions of aws-serverless-mcp-server before 0.2.1 are affected. To check an installed version, look at the package version in your installation. Reads require the target path to end in a valid JSON file, and writes require the --enable-write flag.Source: github.com
What should I do about it?
Upgrade to AWS Serverless MCP Server 0.2.1, the version the advisory says addresses this issue.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data