Non-exit on Failed Initialization Affecting awslabs.aws-api-mcp-server package, versions [0.2.13,1.3.47)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-PYTHON-AWSLABSAWSAPIMCPSERVER-18319690
- published26 Jul 2026
- disclosed24 Jul 2026
- creditUnknown
Introduced: 24 Jul 2026
NewCVE-2026-16584 (opens in a new tab)How to fix?
Upgrade awslabs.aws-api-mcp-server to version 1.3.47 or higher.
Overview
awslabs.aws-api-mcp-server is a Model Context Protocol (MCP) server for interacting with AWS
Affected versions of this package are vulnerable to Non-exit on Failed Initialization in the startup initialization process. An attacker can gain unauthorized access to restricted AWS API operations by exploiting a failure in loading security policy enforcement data at server startup, which causes policy checks to be silently skipped for the lifetime of the process.
Workaround
This vulnerability can be mitigated by using least-privilege IAM credentials or by restarting the server after restoring connectivity to ensure the policy enforcement data loads successfully.