High 7.8Published Oct 27, 2026

CVE-2026-115413AWS API MCP Server OAuth Token Audience Validation Bypass

Updated under an hour ago (Oct 28, 2026, 2:00 PM ET)

Does this affect you?

It affects aws-api-mcp-server. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for aws-api-mcp-server

Exploited in the last 30 days

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.

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): CWE-346
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: AMZN
NVD analysis: Awaiting Analysis
Record last updated: Oct 27, 2026
First seen by InfoSec Signals: Oct 27, 2026

Affected products

Affected products

AWS aws-api-mcp-server aws:api_mcp_server (from the name)	from 1.3.0 before 1.6.0	CNA record

References

References

https://pypi.org/project/awslabs.aws-api-mcp-server/1.6.0/	release-notes, patch
https://github.com/awslabs/mcp/security/advisories/GHSA-4prq-p2x5-w9fh	third-party-advisory
https://aws.amazon.com/security/security-bulletins/2026-152-aws/	vendor-advisory

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.