GHSA-2f9r-g4f3-wc2j · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
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.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams running the AWS Labs Timestream for InfluxDB MCP Server in versions from 0.0.12 up to but not including 0.0.19, especially where MCP clients process untrusted content. Forked or derivative code must also be patched. The sources do not say whether managed hosting changes exposure.
Not affected if version-0.0.19-or-later
Who cares aws, influxdb, lab-disclosure, mcp, python
awslabs.timestream-for-influxdb-mcp-server; affected versions are >=0.0.12 and <0.0.19.awslabs.timestream-for-influxdb-mcp-server 0.0.19CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS
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:
Acknowledgement:
We would like to thank @Yuremin, @FORIMOC and @invoke1442 for collaborating on this issue through the coordinated vulnerability disclosure process.
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.
Please email aws-security@amazon.com with any s ecurity questions or concerns.