UTC
High

AWS API MCP Server Security Policy Bypass via Startup Initialization Failure

CVE-2026-16584 · GHSA-29w2-fq35-v728 · published 2026-07-24

Severity
High
CVSS score
7.0
Chance of exploitation (EPSS)
0.23%
Fixed in
1.3.47
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Total
  • CISA SSVC
What it is

On startup, the server loads data used to enforce the configured security policy. If that load fails, the server continues running without the enforcement data in place. In the default configuration, the per-request security check is then bypassed for the lifetime of the process: configured deny and gate rules are not consulted, and AWS API operations the policy was intended to restrict execute without enforcement. The scope is limited to the security-policy gate; IAM permissions on the configured credentials remain in effect and continue to bound what the server can do. Impacted versions: >= 0.2.13 AND < 1.3.47

What to do

Upgrade awslabs-aws-api-mcp-server to 1.3.47 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

This issue has been addressed in awslabs.aws-api-mcp-server version 1.3.47. AWS recommends upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes.

If you cannot upgrade yet

Any one of the following prevents the bypass until you can upgrade: Use least-privilege IAM credentials (for example, a ReadOnlyAccess role) scoped to the task. IAM remains the primary access control and is enforced regardless of this issue. If the server started during degraded connectivity, restart it once connectivity is restored so the policy enforcement data loads successfully.

Affected
PackageRegistryAffectedFixed in
awslabs-aws-api-mcp-serverPyPI>= 0.2.13, < 1.3.471.3.47
Also in awslabs-aws-api-mcp-server
  1. MediumAWS API MCP File Access Restriction Bypassawslabs-aws-api-mcp-server

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].