CVE-2026-126816 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
The cost report generator in AWS Pricing MCP Server accepts absolute paths or directory traversal sequences in its report output path, so content the AI agent controls can be written outside the intended output directory. The tool is also annotated as read-only, so MCP clients may auto-approve it without asking the user.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running the AWS Pricing MCP Server or the deprecated cost-analysis MCP server with an AI assistant that can call the cost report tool. The risk depends on the agent being influenced by untrusted content; teams on 1.0.31 or later, or not using this server, can skip it.
Not affected if server-not-installed, version-1.0.31-or-later
Who cares aws, claude-code, lab-disclosure, mcp, python
awslabs.aws-pricing-mcp-server with pip show awslabs.aws-pricing-mcp-server; versions below 1.0.31 are affected.awslabs.cost-analysis-mcp-server package is installed; versions <= 1.0.5 are affected.generate_cost_report.CVE-2026-126816 Bulletin for AWS Pricing MCP Server - AWS
Bulletin ID: 2026-184-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/16/2026 12:00 PM PST
Description:
AWS Pricing MCP Server is an open source Model Context Protocol (MCP) server that provides real-time AWS pricing information and cost analysis capabilities to AI assistants.
We identified CVE-2026-126816, an issue in the cost report generation tool of AWS Pricing MCP Server before version 1.0.31. An actor who can influence the MCP agent might be able to write actor controlled content to locations outside the intended output directory via absolute paths or directory traversal sequences in the report output path. The tool was also annotated as read-only, which can lead MCP clients to auto-approve it without user confirmation.
Impacted versions:
Resolution:
This issue has been addressed in awslabs.aws-pricing-mcp-server version 1.0.31. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Users of the deprecated awslabs.cost-analysis-mcp-server package should migrate to awslabs.aws-pricing-mcp-server version 1.0.31 or later, as no patched release of that package will be published.
Workarounds:
Users unable to upgrade should remove generate_cost_report from any auto-approve configuration in their MCP client, so that each invocation requires explicit confirmation and the output path can be checked before approving. Users should also avoid passing untrusted content to the agent.
References:
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
awslabs.aws-pricing-mcp-server: upgrade to 1.0.31 or later.awslabs.cost-analysis-mcp-server: no patched release will be published; migrate to awslabs.aws-pricing-mcp-server 1.0.31 or later.Acknowledgement:
We would like to thank Ryan von Brubeck for collaborating on this issue through the coordinated vulnerability disclosure process.
Please email aws-security@amazon.com with any s ecurity questions or concerns.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.