CVE-2026-126681: Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server
Improper restriction of intended endpoints in the connection configuration handling of the AWS Labs Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) before 0.0.19 might allow a remote unauthenticated actor (via prompt injection) to obtain the InfluxDB API token configured on the server, sent to a crafted endpoint controlled through an InfluxDB URL introduced in the MCP client context.
To remediate this issue, users should upgrade to version 0.0.19 or later and rotate any InfluxDB API tokens configured for the server.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
awslabs.timestream-for-influxdb-mcp-serverto a version that resolves this vulnerability.Fixed in 0.0.19 - Operational
Rotate any InfluxDB API tokens configured for the server.
Event History
Frequently Asked Questions
Which deployments are affected?
Deployments of awslabs.timestream-for-influxdb-mcp-server before version 0.0.19 are affected when an InfluxDB API token is configured on the server.
What does exploitation require?
A remote unauthenticated actor must be able to use prompt injection to introduce an attacker-controlled InfluxDB URL into the MCP client context. The server can then send its configured InfluxDB API token to that crafted endpoint.
What should be done after upgrading?
Upgrade to version 0.0.19 or later and rotate any InfluxDB API tokens configured for the server. Token rotation is required because tokens may have been exposed before remediation.