Skip to main content
VulnerabilityPublished

CVE-2026-115413: aws-api-mcp-server · Origin Validation Error

Affects aws-api-mcp-serverSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High : upgrade to 1.6.0 soon.

Data as of 27 Oct 2026, 18:42 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.6.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade aws-api-mcp-server and awslabs-aws-api-mcp-server to 1.6.0.

Affected software

ProductAffectedFixed in
AWSaws-api-mcp-serverAffected
  • >=1.3.0 <1.6.0
Fixed in
  • 1.6.0
PyPIawslabs-aws-api-mcp-serverpkg:pypi/awslabs-aws-api-mcp-serverOther threatsAffected
  • >=1.3.0 <1.6.0
Fixed in
  • 1.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade aws-api-mcp-server to version 1.6.0 or later, which includes the fix for this vulnerability. Additionally, they must configure the expected token audience or client ID for the server to ensure proper token validation. Since this is a server-side component, applying the official fix fully mitigates the issue.

Description

CVE-2026-115413 is a vulnerability in AWS aws-api-mcp-server versions 1.3.0 up to but not including 1.6.0. It involves missing token audience validation in the OAuth authentication mode, which could allow local users to perform AWS operations using the server's configured AWS credentials with an access token issued to another application by the same identity provider. The issue is fixed in version 1.6.0 by adding proper token audience or client ID validation.

Reports on CVE-2026-115413

References

Community reviews

Loading reviews…