Description
Missing token audience validation in the OAuth authentication mode of AWS API MCP Server before version 1.6.0 might allow local users to run AWS operations with the server's configured AWS credentials via an access token issued to another application by the same identity provider.



To remediate this issue, users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.
Published: 2026-10-27
Score: 7.3 High
EPSS: n/a
KEV: No
Impact: Unauthorized use of AWS server credentials by local users
Action: Apply Patch
AI Analysis

Impact

The vulnerability is a missing token audience validation in the OAuth authentication path of AWS API MCP Server. An attacker who can obtain an access token issued to a different application by the same identity provider can present that token to the server without rejection. This allows a local user to execute AWS operations with the server’s configured permissions, effectively gaining privileged access to AWS resources that the server is authorized to manipulate.

Affected Systems

Amazon Web Services, product AWS API MCP Server, versions prior to 1.6.0 on any supported platform, regardless of operating system or deployment method.

Risk and Exploitability

The CVSS score of 7.3 classifies the issue as high severity, indicating significant risk if exploited. The EPSS score is not available, so precise exploit probability cannot be quantified, but the absence of a Public KEV listing suggests no known public exploitation yet. The likely attack vector is local or internal: a user who can obtain a valid OAuth token from the same identity provider can craft a request to the server and bypass audience checks to perform arbitrary AWS calls using privileged credentials.

Generated by OpenCVE AI on October 27, 2026 at 19:17 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the AWS API MCP Server to version 1.6.0 or later.
  • Configure the server to enforce the expected token audience or client ID for incoming OAuth tokens.
  • Review and adjust the identity provider’s token issuance policies so that tokens are issued only to the intended audience and verify that the server’s audience configuration matches the provider settings.

Generated by OpenCVE AI on October 27, 2026 at 19:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 27 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
Description Missing token audience validation in the OAuth authentication mode of AWS API MCP Server before version 1.6.0 might allow local users to run AWS operations with the server's configured AWS credentials via an access token issued to another application by the same identity provider. To remediate this issue, users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.
Title AWS API MCP Server OAuth Token Audience Validation Bypass
First Time appeared Aws
Aws aws-api-mcp-server
Weaknesses CWE-346
CPEs cpe:2.3:a:aws:aws-api-mcp-server:*:*:*:*:*:*:*:*
Vendors & Products Aws
Aws aws-api-mcp-server
References
Metrics cvssV3_1

{'score': 7.8, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 7.3, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

Aws Aws-api-mcp-server
cve-icon MITRE

Status: PUBLISHED

Assigner: AMZN

Published:

Updated: 2026-10-27T18:10:28.758Z

Reserved: 2026-10-22T13:11:03.305Z

Link: CVE-2026-115413

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-27T19:17:10.593

Modified: 2026-10-27T19:17:10.593

Link: CVE-2026-115413

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-27T20:30:08Z

Weaknesses