CVE-2026-126681
AWS Timestream MCP could send an InfluxDB token to an attacker-selected endpoint
AWS · AWS Labs Timestream for InfluxDB MCP Server
First documented disclosure · Review checkpoint
Summary
Prompt-influenced connection settings could redirect an InfluxDB credential to an unintended server.
Severity and exploitation evidence
Medium · 6.8/10 · CVSS 4.0. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
Endpoint selection accepted an untrusted URL introduced in MCP client context.
Conditions required
An actor can influence client context through prompt injection and the server has an InfluxDB API token.
Potential impact
The configured InfluxDB API token can be disclosed.
Affected versions and configurations
0.0.12 through versions before 0.0.19.
Fix and mitigation status
0.0.19.
Practical next steps
Upgrade to 0.0.19 or later and rotate any InfluxDB API tokens configured for the server.
Operating lesson
Bind database credentials to approved endpoints.
Evidence and limits
The CNA and AWS bulletin establish the corrected range. One GitHub package table reverses its affected and fixed columns.
Sources
- AMZN CVE authority record
Primary source ·
- AWS Labs Timestream for InfluxDB MCP Server original advisory
Primary source ·
- ENISA EUVD-2026-126645
Primary source ·