CVE-2026-126681

Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server

Published Nov 16, 2026 CVSS 4.0 · 6.8 Medium EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability arises from the MCP Server’s connection configuration handling, which fails to enforce restrictions on the intended endpoints. A remote unauthenticated actor, using prompt injection techniques, can cause the server to send the stored InfluxDB API token to a crafted endpoint controlled through an InfluxDB URL supplied by the client. The exposure of the API token grants full access to any InfluxDB resources that the token permits. This flaw can lead to unauthorized data exfiltration, modification, or destruction, affecting confidentiality, integrity, and availability of time‑series data.

Affected Systems

AWS Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) versions prior to 0.0.19.

Risk and Exploitability

With a CVSS score of 6.8, the vulnerability is considered moderate‑severity. No EPSS score is available, and the issue is not listed in the CISA KEV catalog. The fix is available in 0.0.19, and no authentication is required to exploit the flaw, making it feasible for any remote actor who can send an InfluxDB URL to a client context.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to AWS Labs Timestream for InfluxDB MCP Server version 0.0.19 or later.
  • Rotate any InfluxDB API tokens that were configured on the server after the upgrade.
  • Restrict the MCP Server’s exposure to prevent arbitrary InfluxDB URLs from being sent in client contexts, ensuring that only trusted endpoints are accepted.

Generated by OpenCVE AI on November 16, 2026 at 21:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server
First Time appeared Aws
Aws timestream-for-influxdb-mcp-server
Weaknesses CWE-923
CPEs cpe:2.3:a:aws:timestream-for-influxdb-mcp-server:*:*:*:*:*:*:*:*
Vendors & Products Aws
Aws timestream-for-influxdb-mcp-server
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 6.8, 'vector': 'CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-923

    Improper Restriction of Communication Channel to Intended Endpoints

Sources

Status
PUBLISHED
Assigner
AMZN
Published
Updated
Nov 16, 2026, 8:59 PM
Reserved
Nov 11, 2026, 2:19 PM
Status
Received
Published
Nov 16, 2026, 9:17 PM
Modified
Nov 16, 2026, 9:17 PM