AI Stack Alert High CVE-2026-115413 For CISO, SOC / IR, AppSec, AI Eng AI-assisted
CVE-2026-115413: AWS API MCP Server OAuth mode lacks token audience validation (pre-1.6.0)
AWS API MCP Server versions before 1.6.0 do not validate token audience in OAuth authentication mode. A local user can use an access token issued to another application by the same identity provider to run AWS operations with the server's configured AWS credentials. The source gives a CVSS base score of 7.3.
Why it matters
Any local user holding a token from another app on the same identity provider may invoke AWS actions under the server's credentials. This can expose AWS resources beyond what that user is authorized to access.
Do this
- Upgrade AWS API MCP Server to version 1.6.0 or later.
- Configure the expected token audience or client ID for the server as part of the upgrade.
- Review which AWS credentials the MCP server uses and reduce them to least privilege.
- Audit MCP server logs for AWS operations that originate from unexpected client identities or tokens.
Exploit Clock
Exploitation unlikely (for now)
- EPSS 0.10%
Signals
- NoCISA KEV
- 7.3CVSS
- 0.10%EPSS
- NoPublic PoC
- 34/100Priority
- 70%Confidence
Evidence
“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”
“users should upgrade to version 1.6.0 and configure the expected token audience or client ID for the server.”
Sources
Affected / related
AWS API MCP Server, Amazon Web Services
Published 2026-10-27 19:17 UTC · updated 2026-11-08 02:39 UTC · AI-assisted summary, checked against quoted sources · How we score