AWS’s MCP server could send InfluxDB token to an attacker’s server
Through prompt injection, AWS’s Timestream for InfluxDB MCP server could send an InfluxDB API token to an attacker. The flaw is fixed in version 0.0.19, and AWS urges users to rotate their tokens. FastMCP 4.2.1 tightens OAuth and JWT checks.
AWS published an advisory on 16 November about vulnerability CVE-2026-126681 in the open-source Timestream for InfluxDB MCP server. The server lets AI assistants and other MCP clients manage Amazon Timestream for InfluxDB resources and read and write InfluxDB data.
AWS said the server did not restrict which endpoints it connected to. Without authenticating, an attacker could use prompt injection, embedding instructions in content the assistant processes. Those instructions could place an attacker-crafted InfluxDB endpoint in the assistant’s context. The server could then send the API token from its configuration to an endpoint the attacker controls.
The flaw affects versions from 0.0.12 onwards and is fixed in version 0.0.19. As well as updating, AWS urges users to rotate any InfluxDB tokens used with a vulnerable version. It also recommends applying the fixes to forks and derivatives of the server code.
AWS said no workaround offers full protection. Until users update, it advises them to use a token with only the necessary permissions and to avoid using the server in MCP clients that process untrusted content.
FastMCP version 4.2.1, released on 17 November, tightens token checks. Its developers describe it as a security and bug-fix release. It no longer accepts a JWT, a signed access token, before the activation time set in its nbf field. The provider’s required scopes are now kept when a custom token verifier is used. Pre-registered OAuth clients can also be pinned to a specific issuer. The release hardens consent handling in the OAuth proxy, forwarding of authorisation server metadata and handling of upstream claims.
The release also raises the minimum version of the opentelemetry-api dependency to exclude a ReDoS vulnerability in the traceparent header. Users who installed FastMCP with pip and also use opentelemetry-sdk should update both with pip install -U fastmcp opentelemetry-sdk. If consent is set to be remembered (require_authorization_consent="remember"), users will be asked for consent once more for each client after the update. The release also includes other security fixes, bug fixes and dependency updates.
Read more: How an agent works · Agent map