AWS fixes two MCP server bugs: prompt injection could make the Timestream for InfluxDB MCP server send its API token to an attacker, and a 'read-only' pricing tool could write files anywhere
- Upgrade: awslabs.timestream-for-influxdb-mcp-server 0.0.19; awslabs.aws-pricing-mcp-server 1.0.31. Move off awslabs.cost-analysis-mcp-server.
- Rotate any InfluxDB API tokens used with affected versions, and use least-privilege tokens.
- Pattern to watch: tool annotations like read-only are hints the server makes about itself. A wrong hint turns client auto-approval into an unreviewed file write.
- Workaround (AWS): remove
generate_cost_reportfrom auto-approve lists and keep untrusted content away from agents using these servers.
Sources: AWS Security Bulletin 2026-185-AWS: CVE-2026-126681, improper restriction of endpoints in Timestream for InfluxDB MCP Server (Nov 16, 2026) · AWS Security Bulletin 2026-184-AWS: CVE-2026-126816, path traversal and arbitrary file write in aws-pricing-mcp-server (Nov 16, 2026) · awslabs/mcp GHSA-2f9r-g4f3-wc2j