---
id: "GHSA-2f9r-g4f3-wc2j"
page: "https://infrastack.ai/live/GHSA-2f9r-g4f3-wc2j"
kind: "vulnerability"
aliases: ["GHSA-2f9r-g4f3-wc2j"]
title: "CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS"
severity: "high"
cvss: null
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "aws", "influxdb", "lab-disclosure", "mcp", "python"]
not_affected_if: ["version-0.0.19-or-later"]
published_at: "2026-11-16T00:00:00+00:00"
first_seen_at: "2026-11-16T21:24:03+00:00"
updated_at: "2026-11-16T21:25:19+00:00"
sources: [{"source": "lab", "url": "https://aws.amazon.com/security/security-bulletins/2026-185-aws/", "first_seen_at": "2026-11-16T21:24:03+00:00"}]
exploit_sources: []
---

# CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS

Link for people: https://infrastack.ai/live/GHSA-2f9r-g4f3-wc2j (this .md is for agents)

The AWS Labs Timestream for InfluxDB MCP Server does not restrict which endpoints it connects to. A remote unauthenticated attacker using prompt injection can make it send its configured InfluxDB API token to an endpoint the attacker controls.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version of `awslabs.timestream-for-influxdb-mcp-server`; affected versions are `>=0.0.12` and `<0.0.19`.
- Look for the InfluxDB API token configured for the server and any MCP clients that process untrusted content.

## Fix

- `awslabs.timestream-for-influxdb-mcp-server` `0.0.19`
- Rotate any InfluxDB API tokens configured for the server after upgrading.

## Timeline

- 2026-11-16T21:24:03+00:00 lab https://aws.amazon.com/security/security-bulletins/2026-185-aws/ — AWS: CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS

## Documents

- [advisory] AWS: CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS https://aws.amazon.com/security/security-bulletins/2026-185-aws/

## From the sources

CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS

### CVE-2026-126681 - Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server

Bulletin ID: 2026-185-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/16/2026 12:30 PM PST

 Description:

The AWS Labs Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) is an open source Model Context Protocol (MCP) server that lets MCP clients, such as AI assistants, manage Amazon Timestream for InfluxDB resources and read and write InfluxDB data. We identified CVE-2026-126681, an issue in how the server handles connection configuration. The server did not restrict which endpoints it connects to. A remote unauthenticated actor could use prompt injection to introduce a crafted InfluxDB URL into the MCP client context. The server could then send its configured InfluxDB API token to an endpoint the actor controls confirmation.

Impacted versions: >=0.0.12 AND <0.0.19

Resolution:

This issue has been addressed in awslabs.timestream-for-influxdb-mcp-server version 0.0.19. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Customers who used an affected version should also rotate any InfluxDB API tokens configured for the server.

Workarounds:

There is no workaround that fully fixes this issue. Until you can upgrade, use an InfluxDB API token with the least permissions needed. Avoid using the server with MCP clients that process untrusted content.

References:

- CVE-2026-126681
- GHSA-2f9r-g4f3-wc2j

Acknowledgement:

We would like to thank @Yuremin, @FORIMOC and @invoke1442 for collaborating on this issue through the coordinated vulnerability disclosure process.

 Please email aws-security@amazon.com with any s ecurity questions or concerns.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
