AWS Pricing MCP Server Fixes Report Path Traversal and Unsafe Auto-Approval

P2 — VALIDATE AND UPDATEModerate · 5.5 (CVSS v3.1, AWS project advisory)EXPLOITATION: NOT STATED

Quick Answer

Upgrade AWS Pricing MCP Server to 1.0.31 or later. Migrate the deprecated cost-analysis server and review generate_cost_report auto-approval rules.

Confirm Scope And Apply The Supported Remediation

What to do now: Inventory resolved MCP package versions, launch commands, service accounts, output directories and clients allowed to invoke generate_cost_report. Determine whether agents read untrusted documents or other external content and can invoke this tool. Limit review to files writable by the local MCP process; the project states that managed AWS services are not affected. Install 1.0.31 or later and patch forks. Migrate cost-analysis-mcp-server users to that package. Until upgraded, require explicit confirmation for generate_cost_report and inspect its output path; avoid untrusted agent input. Test that absolute paths, traversal segments and escaping symlinks are rejected. Confirm the output base directory and write-tool approval behavior. Retain package hashes, MCP configuration, file-change logs and regression results.

Open the authoritative advisory

Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeAWS Pricing MCP Server and the deprecated AWS Cost Analysis MCP Server
Advisory2026-184-AWS / GHSA-mqm3-w68j-75mw
CVECVE-2026-126816
Authoritative release date2026-11-16T20:00:00Z — original authoritative release time in UTC.
Authority revision dateNo separate material advisory revision is confirmed.
Affected versionsawslabs.aws-pricing-mcp-server before 1.0.31; awslabs.cost-analysis-mcp-server through 1.0.5. Exposure requires a locally installed server and an agent that processes attacker-influenced content.
Fixed versionawslabs.aws-pricing-mcp-server 1.0.31 or later; migrate from the deprecated cost-analysis package, which will not receive a patched release
CVSS base score5.5 (CVSS v3.1, AWS project advisory)
CVSS severityModerate
Exploitation statusThe cited authority does not confirm exploitation in the wild.; no exploitation claim is inferred.

What Changed

The cost-report tool could write outside its output directory and was incorrectly marked read-only, allowing some MCP clients to approve writes automatically. The fix confines output paths and corrects the tool annotation.

What To Validate Now

  1. Inventory. Inventory resolved MCP package versions, launch commands, service accounts, output directories and clients allowed to invoke generate_cost_report.
  2. Establish applicability. Determine whether agents read untrusted documents or other external content and can invoke this tool. Limit review to files writable by the local MCP process; the project states that managed AWS services are not affected.
  3. Remediate. Install 1.0.31 or later and patch forks. Migrate cost-analysis-mcp-server users to that package. Until upgraded, require explicit confirmation for generate_cost_report and inspect its output path; avoid untrusted agent input.
  4. Validate. Test that absolute paths, traversal segments and escaping symlinks are rejected. Confirm the output base directory and write-tool approval behavior. Retain package hashes, MCP configuration, file-change logs and regression results.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Changing approval rules is an interim control. Review AWS_PRICING_MCP_OUTPUT_DIR and working-directory permissions after upgrading; a path confined to an overly broad writable directory can still be operationally unsafe.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.