Quick answers
- Is CVE-2026-16584 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16584 being exploited in the wild.
- How severe is CVE-2026-16584?
- High severity, with a CVSS score of 7, published 23 July 2026.
- Which products and versions are affected?
- Aws-Api-Mcp-Server >= 0.2.13, < 1.3.47; awslabs.aws-api-mcp-server (PyPI) >= 0.2.13, < 1.3.47, ECOSYSTEM:introduced=0.2.13,fixed=1.3.47.
- Is there a fix for CVE-2026-16584?
- Yes. awslabs.aws-api-mcp-server (PyPI): upgrade to 1.3.47 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16584 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-16584?
- Check whether you run Amazon AWS, AWS API MCP Server, Aws-Api-Mcp-Server or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- awslabs.aws-api-mcp-server (PyPI): upgrade to 1.3.47 or later
pip install "awslabs.aws-api-mcp-server>=1.3.47"
Technical details
CVE-2026-16584 describes a security policy bypass vulnerability in AWS API MCP Server that occurs during startup failure scenarios. The vulnerability allows an attacker to circumvent security policy enforcement when the server fails to start properly. The exact attack vector and preconditions are not fully detailed in the available advisory content, but the issue likely affects deployments where startup failures are not properly handled or validated. AWS has published this as a high-severity issue and users should apply any available patches or security updates to affected deployments.
Affected products
- AWS API MCP Server
Identifiers
- CVE-2026-16584
- GHSA-29w2-fq35-v728
- PYSEC-2026-3549
Timeline
- 2026-09-22: disclosed