What happened
In the AWS Labs Timestream for InfluxDB MCP Server before 0.0.19, the connection-configuration handling does not restrict the endpoints the server may connect to (CWE-923, CVSS 5.5). A remote unauthenticated actor can use prompt injection to introduce a crafted InfluxDB URL, causing the server to send its configured InfluxDB API token to an attacker-controlled host. Fixed in 0.0.19 (AWS Security Bulletin 2026-185-AWS).
Why it matters
This is an MCP-server credential exfiltration driven by injected prompt content: the model is the vector that steers the server into leaking a real database credential. Victims must rotate the InfluxDB API token, since an exposed token grants access to customer InfluxDB data at its granted permission level.
Attack vector
Prompt-injected content steers the MCP server's connection configuration to an attacker-controlled InfluxDB URL; the server sends its configured InfluxDB API token on connect
Affected systems
awslabs.timestream-for-influxdb-mcp-server before 0.0.19
Mitigation
Upgrade to 0.0.19+ (pip install awslabs.timestream-for-influxdb-mcp-server==0.0.19) and rotate any InfluxDB API token configured for the server