Skip to main content
Menu
CVEs

CVE

aws-pricing-mcp-server arbitrary file write in cost report generator

CVE-2026-126816EUVD-2026-126627

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

5.5MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.31
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.0.31.

Published
Last modified
Reference
Last checked
6/100 · provisional
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

A path traversal flaw in the cost report generator of AWS's aws-pricing-mcp-server, and the older cost-analysis-mcp-server package, lets an attacker write attacker-controlled content to locations outside the intended output directory. The attacker must be able to act locally, without logging in, by influencing the MCP agent to use absolute paths or directory traversal sequences in the report output path, and a user must take an action for this to happen.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Improper limitation of a pathname to a restricted directory in the cost report generation tool in AWS Pricing MCP Server (aws-pricing-mcp-server) before 1.0.31 might allow an actor who can influence the MCP agent to write actor controlled content to arbitrary locations outside the intended output directory via absolute paths or directory traversal sequences in the report output path.

To remediate this issue, users should upgrade to version 1.0.31 or later. Users of the deprecated awslabs.cost-analysis-mcp-server package should migrate to awslabs.aws-pricing-mcp-server version 1.0.31 or later.

cve.now Index

6Pcve.now Index 6 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.5/10CVSS 5.5
  • No patch0/5No signal

What would change the score

  • Would score about 61 if added to CISA KEV
  • Would score about 56 if CISA's SSVC rates exploitation active
  • Would score about 28 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.0.31.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126816 (Path traversal and arbitrary file write in the cost report generator of aws-pricing-mcp-server), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126816 (entry last updated 2026-11-16):
Affected:
- AWS aws-pricing-mcp-server: fixed in 1.0.31
- AWS cost-analysis-mcp-server: through 1.0.5
Fixed versions: 1.0.31.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126816 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126816 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://aws.amazon.com/security/security-bulletins/2026-184-aws/
- https://pypi.org/project/awslabs.aws-pricing-mcp-server/1.0.31/
- https://github.com/awslabs/mcp/security/advisories/GHSA-mqm3-w68j-75mw
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126816
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126816"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • AWS aws-pricing-mcp-server

    fixed in 1.0.31

  • AWS cost-analysis-mcp-server

    through 1.0.5

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Advisory
  2. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126816

Is CVE-2026-126816 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-126816?

aws-pricing-mcp-server: before 1.0.31. cost-analysis-mcp-server: through 1.0.5.Source: cve.now feed data

How do I fix CVE-2026-126816?

Upgrade to a fixed version: 1.0.31.Source: cve.now feed data