Read the docs

AWS API MCP Server Policy Bypass via Operation Name Normalization

Priority LOW 39CWE-1025Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-863.

Summary

The awslabs aws-api-mcp-server package from AWS, from 0.2.13 before 1.5.1, applies its custom security policy with incorrect normalization of operation names. An actor who can call the server can run AWS API operations in services the operator's policy was set to deny or require elicitation for, by using operation names that contain consecutive capital letters. The flaw is tracked as CWE-1025 (comparison using wrong factors) and CWE-863 (incorrect authorization). The CVSS 4.0 vector shows a local attack that needs user interaction, with high impact to confidentiality, integrity and availability.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

Incorrect normalization of operation names in the custom security policy enforcement in awslabs aws-api-mcp-server before 1.5.1 might allow an actor to execute AWS API operations across AWS services that the operator's security policy was configured to deny or require elicitation for, via calls to operations whose names contain consecutive capital letters. To remediate this issue, users should upgrade to version 1.5.1.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00374 31st percentileScored 2026-11-16
Fix Fixed aws-api-mcp-server (AWS): 1.5.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
AWSaws-api-mcp-server0.2.13 to before 1.5.11.5.1Patch availableCNA
  • aws-api-mcp-server VendorAWS Affected 0.2.13 to before 1.5.1 Fixed in 1.5.1 Patch available CNA

Remediation

Upgrade aws-api-mcp-server to version 1.5.1, which is the fixed version.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA aws-api-mcp-server (AWS) Fixed in 1.5.1

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-125271
  2. 2026-11-10 1 new reference · CNA
  3. 2026-11-12 Priority changed: MEDIUM → LOW
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-23989 Incorrect resource transfer in Linux kernel algif_aead KEVCVSS 3.1HIGH 7.8
  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2024-18648 Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM… CVSS 3.1CRITICAL 9.8
  • TI-2024-05929 Openssh: regresshion - race condition in ssh allows rce/dos CVSS 3.1HIGH 8.1
  • TI-2025-03847 Input validation issue in AWS Amplify Studio UI component properties CVSS 4.0CRITICAL 9.0
  • TI-2026-11603 HTTP/2 Stream Parser Confusion Body-Inspection Bypass in Amazon CloudFront with AWS WAF CVSS 4.0HIGH 7.9
See all 397 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences