CVE-2026-126681: AWS timestream-for-influxdb-mcp-server · Improper Restriction of Communication Channel to Intended Endpoints
Affects AWS timestream-for-influxdb-mcp-serverSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 0.0.19 when convenient.
Data as of 16 Nov 2026, 21:04 UTC
Thin evidence
One scorer or none| CNA (AMZN) | CVSS 3.1 | 5.5 |
|---|---|---|
| CNA (AMZN) | CVSS 4.0 | 6.8 |
- Patch
- Available – fixed in 0.0.19
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade AWS timestream-for-influxdb-mcp-server to 0.0.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AWStimestream-for-influxdb-mcp-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the AWS Labs Timestream for InfluxDB MCP Server to version 0.0.19 or later. After upgrading, rotate any InfluxDB API tokens configured on the server to prevent misuse of any tokens potentially exposed prior to the fix. AWS manages remediation for this cloud-hosted service; consult the AWS security advisory for additional guidance.
Description
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.