aws-mcp has a Command Injection Remote Code Execution Vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-5059: 1.91% estimated exploitation activity in the next 30 days; percentile 79.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

aws-mcp-server AWS CLI Command Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of aws-mcp-server. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of the allowed commands list. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of the MCP server. Was ZDI-CAN-27969.

Published by the source

11 Apr 2026, 03:30 UTC

Last modified by the source

27 Oct 2026, 15:30 UTC

Source last checked

28 Oct 2026, 06:10 UTC

1. Revision 5 · amended · 28 Oct 2026

   Amended from osv record GHSA-fgmx-xfp3-w28p

2. Revision 4 · amended · 27 Oct 2026

   Amended from ghsa record GHSA-fgmx-xfp3-w28p

3. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fgmx-xfp3-w28p

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-fgmx-xfp3-w28p

5. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-fgmx-xfp3-w28p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-5059

Advisory: aws-mcp has a Command Injection Remote Code Execution Vulnerability
IDs: CVE-2026-5059, GHSA-fgmx-xfp3-w28p
Record: https://patchnext.com/advisories/cve-2026-5059 (revision 5, source checked 28 Oct 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI aws-mcp: affected <= 1.7.0

## Suggested inspection (read-only)
- `python -m pip show aws-mcp`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on aws-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fgmx-xfp3-w28p (GitHub-reviewed advisory GHSA-fgmx-xfp3-w28p lists affected ranges: PyPI aws-mcp >=0 <=1.7.0)
- Verified: https://osv.dev/vulnerability/GHSA-fgmx-xfp3-w28p (OSV record GHSA-fgmx-xfp3-w28p lists affected ranges: PyPI aws-mcp >=0 <=1.7.0)

Commands are suggestions: review each one before running it.