Live › vulnerability › CVE-2026-115413
Go to dashboardThe AWS API MCP Server in streamable-http mode with OAuth does not check the audience claim of bearer tokens, so a token issued by the same identity provider to a different application in the same tenant is accepted. An attacker holding such a token can make AWS API calls using the credentials configured on the host.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 18:39 UTC, 1h before NVD. All times on this page are UTC.
Exposed deployments run the AWS API MCP Server with the streamable-http transport and OAuth authentication, where the host holds AWS credentials and the identity provider issues tokens to more than one application in the same tenant. Local stdio use is not in the described attack path. Teams on stdio or on versions outside >=1.3.0 and <1.6.0 can skip it.
No product ranges from the sources yet.
pip show awslabs.aws-api-mcp-server or check the installed package version; affected versions are >=1.3.0 and <1.6.0AUTH_TYPE is set to oauth and whether the server runs with the streamable-http transportAUTH_AUDIENCE or AUTH_CLIENT_ID is set1.6.0 or laterAUTH_TYPE=oauth, set AUTH_AUDIENCE, or AUTH_CLIENT_ID for identity providers such as Amazon Cognito whose access tokens carry no audience claimEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
CVE-2026-115413 - AWS API MCP Server OAuth token audience validation bypass
Bulletin ID: 2026-152-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 10/27/2026 11:00 AM PDT
Description:
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 can be configured to serve the streamable-http transport with OAuth authentication, validating a bearer token against an identity provider nominated by the operator. We identified CVE-2026-115413 in versions >=1.3.0 and <1.6.0, the server validates a token's signature, issuer and expiry, but not the claim identifying the application the token was issued for. A token that the nominated identity provider issued to another application in the same tenant is therefore accepted, which may allow AWS API calls to be made with the credentials configured on the host.
Impacted versions: >=1.3.0 AND <1.6.0
Resolution:
This issue has been addressed in awslabs.aws-api-mcp-server version 1.6.0. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Operators using AUTH_TYPE=oauth should also set AUTH_AUDIENCE, or AUTH_CLIENT_ID for identity providers whose access tokens carry no audience claim, such as Amazon Cognito.
Workarounds:
Operators who cannot upgrade immediately can use the default stdio transport rather than the streamable-http transport.
References:
Acknowledgement:
We would like to thank Yuval Elbar (@YuvalElbar6) for collaborating on this issue through the coordinated vulnerability disclosure process.
Please email [email protected] with any security questions or concerns.
This page as .md · .json · in your agent: get_signal("CVE-2026-115413")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.