CVE-2026-116635

Improper limitation of a pathname to a restricted directory in the deployment status component of the AWS Serverless MCP Server

  • Medium 6.9

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.

Key facts

Published
2 Nov 2026
Last changed
6 Nov 2026
Assigned by
AMZN
EPSS
0.313% likely to be exploited in the next 30 days, higher than 24.56% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.1CVSS 3.1, Mediumfrom the CNA (AMZN)CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N
  • 6.9CVSS 4.0, Mediumfrom the CNA (AMZN)CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

CAPEC-126 Path Traversal (CNA impact statement)

CAPEC-597 Absolute Path Traversal (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
AWSaws-serverless-mcp-server
  • Default status: unaffected
  • 0 up to but excluding 0.2.1 (affected)

Timeline

  1. 2 Nov 2026 Published

Weakness

References