cve.bz

CVE-2026-126681 Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server

6.8 medium

Medium (6.8) in aws timestream-for-influxdb-mcp-server.

On this page
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.

Severity

CVSS 4.0

6.8 medium
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

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CWE
CWE-923 Improper Restriction of Communication Channel to Intended Endpoints
Published
Assigned by
AMZN (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126681 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126681?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126681?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126681 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
AWS timestream-for-influxdb-mcp-serverfrom 0.0.12 before 0.0.19

Attack patterns (CAPEC)

  • CAPEC-161 Infrastructure Manipulation Severity: High
  • CAPEC-481 Contradictory Destinations in Traffic Routing Schemes Likelihood: Medium · Severity: High
  • CAPEC-501 Android Activity Hijack Severity: Medium
  • CAPEC-697 DHCP Spoofing Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON