AWS repairs a file write bug in its Pricing MCP server
A tool that the software marked read-only could write files in other folders, and clients could operate it with no user check.
On 16 November 2026, Amazon gave a bulletin for bug CVE-2026-126816 in its AWS Pricing MCP Server, and version 1.0.31 repairs it. The open source server gives AI assistants live AWS prices and cost analysis, and versions before 1.0.31 have the bug. MCP, the Model Context Protocol, is a standard that lets AI agents use other tools.
How it works
The cost report tool did not limit the output path. A person who can influence the AI agent could write content in other folders. They could use absolute paths or directory traversal sequences, which are path parts that go to other folders.
The tool was also marked read-only. Because of this, MCP clients can operate it with no user confirmation.
The numbers
The bulletin gives no severity score and no report of an attack. It names these packages:
- the pricing server package, before version 1.0.31
- the cost-analysis server package, version 1.0.5 and before
What is not known
AWS does not tell how an attacker could use the written files. AWS will not publish a patch for the cost-analysis package. Its users must move to the pricing server, version 1.0.31 or after. Ryan von Brubeck reported the bug in a coordinated disclosure.
Insight: One label can turn off a user check
3 AWS bulletins on MCP tools came before this one. They were a token bug on 27 October, a file write bug on 30 October and a gateway bug on 11 November. Here the read-only label made clients skip the user check, which reads as an approval step that follows the label of the tool. For leaders: a label is only a statement, not a control.
Sources
- CVE-2026-126816Path traversal and arbitrary file write in the cost report generator of aws-pricing-mcp-server
Posted