CVE-2026-16584: Awslabs.aws api mcp server AWS API MCP Server Security Vulnerability

HIGH
Advisory Identifier: GHSA-29w2-fq35-v728
CVSS 7.0
CWE-455
Published
Advisory Summary

CVE-2026-16584 is a HIGH (CVSS 7.0) aws api mcp server security vulnerability (CWE-455: Non-exit on Failed Initialization) affecting Awslabs.aws api mcp server libraries in the PyPI ecosystem. The issue involves aws api mcp server security policy bypass via startup initialization failure. Remediation is available by upgrading affected packages to version 1.3.47.

CVE-2026-16584 at a Glance

CVE Identifier CVE-2026-16584
GHSA Identifier GHSA-29w2-fq35-v728
Severity HIGH
CVSS v3.1 Base Score 7.0
CWE Classification CWE-455: Non-exit on Failed Initialization
Affected Product Awslabs.aws api mcp server
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 7.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H).

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-16584

To remediate this vulnerability, upgrade all affected Awslabs.aws api mcp server dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

awslabs.aws-api-mcp-server fixed: 1.3.47
pip install awslabs.aws-api-mcp-server>=1.3.47
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show awslabs.aws-api-mcp-server

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-16584, inspect your installed packages using pip:

pip show awslabs.aws-api-mcp-server

Analyze the terminal output to locate any version of Awslabs.aws api mcp server in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.47), your application is affected.

Note: The pip show awslabs.aws-api-mcp-server command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-455: Non-exit on Failed Initialization, where the product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (hsm) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator. In Awslabs.aws api mcp server, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process. ### Impact 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 ### Patches 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. ### Workarounds 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. ### Contact If you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the [reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue. ### Acknowledgement We would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process.

CVE-2026-16584 Affected Awslabs.aws api mcp server Versions

1 component(s)
Fixed Versions:
1.3.47
Product / Package Ecosystem Affected Versions Fixed Version
awslabs.aws-api-mcp-server
PyPI
≥ 0.2.13
< 1.3.47
1.3.47

References

Frequently Asked Questions

What is CVE-2026-16584?
CVE-2026-16584 is a security vulnerability in Awslabs.aws api mcp server involving AWS API MCP Server Security Policy Bypass via Startup Initialization Failure under CWE-455: Non-exit on Failed Initialization.
Which Awslabs.aws api mcp server versions are affected?
Affected versions include releases prior to 1.3.47 across affected packages: awslabs.aws-api-mcp-server.
What version fixes CVE-2026-16584?
Upgrading to 1.3.47 (or the latest patched release for your respective branch) resolves the vulnerability.
Is awslabs.aws-api-mcp-server affected?
Yes, awslabs.aws-api-mcp-server is affected in releases prior to 1.3.47. Upgrade your dependency to 1.3.47 or later.
What is the CVSS score of CVE-2026-16584?
CVE-2026-16584 has a CVSS v3.1 base score of 7.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-16584?
CVE-2026-16584 is classified under CWE-455: Non-exit on Failed Initialization (The product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (HSM) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator.).
How can I check PyPI dependencies for CVE-2026-16584?
Run the dependency tree command: 'pip show awslabs.aws-api-mcp-server'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-29w2-fq35-v728",
  "modified" : "2026-07-24T22:33:19Z",
  "published" : "2026-07-24T22:33:19Z",
  "aliases" : [ "CVE-2026-16584" ],
  "summary" : "AWS API MCP Server Security Policy Bypass via Startup Initialization Failure",
  "details" : "## Summary\nThe AWS API MCP Server is an open source Model Context Protocol (MCP) server that enables AI assistants to interact with AWS services and resources through AWS CLI commands. It provides programmatic access to manage your AWS infrastructure while maintaining proper security controls. It includes an optional, user-configured security policy that can deny or gate specific AWS operations. An issue exists where, if the data used to enforce this policy fails to initialize at server startup, the per-request policy check is silently skipped for the lifetime of the process.\n\n### Impact\nOn 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.\n\n**Impacted versions**: >= 0.2.13 AND < 1.3.47\n\n### Patches\nThis 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.\n\n### Workarounds\nAny one of the following prevents the bypass until you can upgrade:\n\n  - 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.\n  - If the server started during degraded connectivity, restart it once connectivity is restored so the policy enforcement data loads successfully.\n\n### Contact\nIf you have any questions or comments about this advisory, AWS asks that you contact AWS Security via the [reporting page](https://aws.amazon.com/security/vulnerability-reporting) or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.\n\n### Acknowledgement\nWe would like to thank Lav Kumar Vishwakarma (independent security researcher) for collaborating on this issue through the coordinated vulnerability disclosure process.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "awslabs.aws-api-mcp-server"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.2.13"
      }, {
        "fixed" : "1.3.47"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/awslabs/mcp/security/advisories/GHSA-29w2-fq35-v728"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-16584"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/awslabs/mcp/pull/4315"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/awslabs/mcp/commit/ab1bbebc097d674c1cdd4bd75a8f313be18473bf"
  }, {
    "type" : "WEB",
    "url" : "https://aws.amazon.com/security/security-bulletins/2026-063-aws"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/awslabs/mcp"
  }, {
    "type" : "WEB",
    "url" : "https://pypi.org/project/awslabs.aws-api-mcp-server/1.3.47"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-455" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T22:33:19Z",
    "nvd_published_at" : "2026-07-23T16:17:15Z"
  }
}