Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding

AWS MCP server let deny lists silently fail

Written November 11, 2026

The AWS API MCP Server let AI assistants manage an AWS account through API calls, with a custom security policy to deny or require confirmation for dangerous operations. A normalization bug meant the policy never matched operations whose names contain consecutive capital letters. The deny list looked like protection. It was not.

The problem

A team that wrote a deny list for its AWS MCP server believed the operations on it were blocked. They were not — the server normalized operation names incorrectly before comparing them to the policy, so entries for affected operations never matched. An assistant could run an operation the operator had configured to deny, such as creating a federated identity provider, deactivating an MFA device, or deleting database clusters.

What the advisory says

The security advisory, tracked as CVE-2026-125271 and rated CVSS 8.5 (High), sets out the scope:

How to check whether you were affected

Two conditions both have to hold: the server version is below 1.5.1, and the custom policy lists operations whose names contain consecutive capital letters. If your deny list only names operations with single capitals or lowercase names, the bug did not touch those entries. If it names an affected operation, that entry never matched — the operation ran as if the list did not exist. There is no error to look for in logs: a deny list that never matches looks exactly like a deny list with nothing to deny.

What to do

Update to 1.5.1. There is no configuration change that fixes this — the advisory states plainly that there is no workaround other than upgrading. After updating, reread your policy entries against the operations they were meant to cover, and treat any operation that ran while on an affected version as having run unprotected. Do not confuse this with a separate AWS MCP issue, CVE-2026-115413, an OAuth token audience validation bypass from October 27, fixed in 1.6.0. Different bug, different fix.

Verdict

Update to 1.5.1. A deny list that never matches is worse than no deny list, because it looks like protection.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: MCP's July spec killed sessions — tooling may not know · Git 2.56.1: patch the recursive-clone bug