Quick answers
- Is CVE-2026-125271 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125271 being exploited in the wild.
- How severe is CVE-2026-125271?
- High severity, with a CVSS score of 7.8, published 10 November 2026.
- Which products and versions are affected?
- AWS API MCP Server 0.2.13 to 1.5.0.
- Is there a fix for CVE-2026-125271?
- Yes: fixed in 1.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125271 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125271?
- Check whether you run Amazon AWS or AWS API MCP Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.5.1
Technical details
The vulnerability exists in the security policy enforcement logic of AWS API MCP Server, where operation names containing consecutive capital letters are incorrectly normalized before being compared against the operator's denyList or elicitList entries. This case-sensitivity issue allows an attacker with access to the MCP server to bypass configured security policies and execute restricted AWS API operations. No user interaction or elevated privileges are required beyond access to the MCP server itself.
Affected products
- AWS API MCP Server 0.2.13 to 1.5.0
Timeline
- 2026-11-10: disclosed
- 2026-11-10: patched