{"id":"CVE-2026-126681","kind":"vulnerability","aliases":["CVE-2026-126681"],"related":[],"title":"Improper restriction of intended endpoints in the connection configuration handling of the AWS Labs Timestream for…","description":"CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS\n\n### CVE-2026-126681 - Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server\n\nBulletin ID: 2026-185-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/16/2026 12:30 PM PST\n\n Description:\n\nThe AWS Labs Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) is an open source Model Context Protocol (MCP) server that lets MCP clients, such as AI assistants, manage Amazon Timestream for InfluxDB resources and read and write InfluxDB data. We identified CVE-2026-126681, an issue in how the server handles connection configuration. The server did not restrict which endpoints it connects to. A remote unauthenticated actor could use prompt injection to introduce a crafted InfluxDB URL into the MCP client context. The server could then send its configured InfluxDB API token to an endpoint the actor controls confirmation.\n\nImpacted versions: >=0.0.12 AND <0.0.19\n\nResolution:\n\nThis issue has been addressed in awslabs.timestream-for-influxdb-mcp-server version 0.0.19. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Customers who used an affected version should also rotate any InfluxDB API tokens configured for the server.\n\nWorkarounds:\n\nThere is no workaround that fully fixes this issue. Until you can upgrade, use an InfluxDB API token with the least permissions needed. Avoid using the server with MCP clients that process untrusted content.\n\nReferences:\n\n- CVE-2026-126681\n- GHSA-2f9r-g4f3-wc2j\n\nAcknowledgement:\n\nWe would like to thank @Yuremin, @FORIMOC and @invoke1442 for collaborating on this issue through the coordinated vulnerability disclosure process.\n\n Please email aws-security@amazon.com with any s ecurity questions or concerns.","summary":"The AWS Labs Timestream for InfluxDB MCP Server did not restrict which endpoints it connects to. A remote attacker using prompt injection can plant a crafted InfluxDB URL so the server sends its configured InfluxDB API token to a server the attacker controls.","severity":"high","cvss":6.8,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"awslabs.timestream-for-influxdb-mcp-server","fixed":[],"affected":"","ecosystem":"pypi"}],"ecosystems":["pypi"],"tags":["ai-tooling","aws","influxdb","lab-disclosure","mcp","python","timestream"],"not_affected_if":["no-influxdb-mcp-server","version-0.0.19-or-later"],"how_to_check":"- Check the installed version of `awslabs.timestream-for-influxdb-mcp-server`; versions `>=0.0.12` and `<0.0.19` are affected.\n- Look for any InfluxDB API token configured for this MCP server, since it may have been exposed.","fix":"- `awslabs.timestream-for-influxdb-mcp-server` `0.0.19`\n- Rotate any InfluxDB API tokens configured for the server after upgrading, per the AWS bulletin.","status":"open","published_at":"2026-11-16T00:00:00+00:00","first_seen_at":"2026-11-16T21:24:03+00:00","triaged_at":"2026-11-16T21:25:19+00:00","updated_at":"2026-11-16T21:38:58+00:00","category":"ai-tooling","confidence":0.8,"triage":{"at":"2026-11-16T21:25:19Z","model":"claude-haiku-5-5","output":{"fix":"- `awslabs.timestream-for-influxdb-mcp-server` `0.0.19`\n- Rotate any InfluxDB API tokens configured for the server after upgrading, per the AWS bulletin.","reach":"internet","title":"AWS Timestream InfluxDB MCP server sends API token to attacker-chosen endpoint","impact":"high","summary":"The AWS Labs Timestream for InfluxDB MCP Server did not restrict which endpoints it connects to. A remote attacker using prompt injection can plant a crafted InfluxDB URL so the server sends its configured InfluxDB API token to a server the attacker controls.","audience":"businesses","category":"ai-tooling","nicknames":[],"who_cares":["mcp","influxdb","timestream","aws","python"],"confidence":0.8,"fix_status":"available","needs_auth":"no","worst_case":"InfluxDB API token is sent to an attacker-controlled endpoint","analyst_note":"","how_to_check":"- Check the installed version of `awslabs.timestream-for-influxdb-mcp-server`; versions `>=0.0.12` and `<0.0.19` are affected.\n- Look for any InfluxDB API token configured for this MCP server, since it may have been exposed.","plain_action":"","product_name":"awslabs.timestream-for-influxdb-mcp-server","needs_analyst":false,"not_affected_if":["version-0.0.19-or-later","no-influxdb-mcp-server"],"who_is_affected":"Teams running the AWS Labs Timestream for InfluxDB MCP server in versions from 0.0.12 up to but not including 0.0.19, connected to MCP clients that process untrusted content. The exposure comes from the server reading an InfluxDB URL supplied through the MCP client context and sending its API token there. Workarounds are limited: use a least-privilege InfluxDB token and avoid untrusted content in the client.","user_interaction":"unknown","product_ecosystem":"pypi","needs_special_setup":"unknown","severity_if_unknown":"high"},"cost_usd":0.000878,"input_tokens":5201,"output_tokens":715,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-126681':18A,21A,84C,93C,174C,326C '-185':110C '-2026':17A,20A,83C,92C,173C,325C '0.0.12':232C '0.0.19':234C,249C '11/16/2026':121C '12':122C '2026':109C '2f9r':329C '30':123C 'acknowledg':332C 'actor':197C,227C 'address':240C 'affect':275C 'ai':29B,156C 'ai-tool':28B 'also':278C 'amazon':159C 'api':74B,221C,282C,305C 'assist':157C 'attack':57B,80B 'attent':118C 'avoid':312C 'aw':13A,31B,40B,87C,90C,100C,111C,113C,128C 'aws-security@amazon.com':355C 'awslabs.timestream':22A,135C,242C 'bulletin':85C,107C 'client':153C,211C,318C 'code':263C 'collabor':343C 'concern':362C 'configur':9A,72B,183C,219C,284C 'confirm':229C 'connect':8A,53B,182C,192C 'content':114C,322C 'context':146C,212C 'control':81B,228C 'coordin':349C 'could':198C,215C 'craft':64B,205C 'custom':271C 'cve':16A,19A,82C,91C,172C,324C 'data':169C 'date':120C 'deriv':262C 'descript':126C 'disclosur':35B,351C 'ecur':359C 'email':354C 'endpoint':5A,51B,98C,190C,225C 'ensur':258C 'fix':270C,295C 'for':24A 'for-influxdb-mcp-serv':136C,243C 'for-influxdb-mcp-server':23A 'forimoc':339C 'fork':260C 'fulli':294C 'g4f3':330C 'ghsa':328C 'ghsa-2f9r-g4f3-wc2j':327C 'handl':10A,181C 'id':108C 'identifi':171C 'impact':230C 'import':116C 'improp':1A,94C 'incorpor':267C 'influxdb':25A,32B,44B,65B,73B,104C,132C,138C,162C,168C,206C,220C,245C,281C,304C 'inject':60B,201C 'intend':4A,97C 'introduc':203C 'invoke1442':341C 'issu':176C,237C,297C,346C 'lab':14A,34B,41B,88C,101C,129C 'lab-disclosur':33B 'latest':255C 'least':309C 'let':151C 'like':335C 'manag':158C 'mcp':26A,36B,45B,105C,133C,139C,148C,152C,210C,246C,317C 'model':145C 'need':311C 'new':269C 'open':143C 'patch':265C 'permiss':310C 'plant':62B 'pleas':353C 'pm':124C 'process':320C,352C 'prompt':59B,200C 'protocol':147C 'pst':125C 'public':119C 'python':37B 'question':360C 'read':165C 'recommend':251C 'refer':323C 'remot':56B,195C 'requir':117C 'resolut':235C 'resourc':163C 'restrict':2A,49B,95C,188C 'rotat':279C 'scope':112C 'send':70B,217C 'server':27A,46B,69B,78B,106C,134C,140C,149C,180C,185C,214C,247C,287C,315C 'sourc':144C 'thank':337C 'timestream':15A,38B,42B,89C,102C,130C,160C 'token':75B,222C,283C,306C 'tool':30B 'type':115C 'unauthent':196C 'untrust':321C 'upgrad':252C,301C 'url':66B,207C 'use':58B,199C,273C,302C,313C 'version':231C,248C,256C,276C 'vulner':350C 'wc2j':331C 'workaround':288C,292C 'would':334C 'write':167C 'yuremin':338C","nicknames":[],"mitigations":[],"who_affected":"Teams running the AWS Labs Timestream for InfluxDB MCP server in versions from 0.0.12 up to but not including 0.0.19, connected to MCP clients that process untrusted content. The exposure comes from the server reading an InfluxDB URL supplied through the MCP client context and sending its API token there. Workarounds are limited: use a least-privilege InfluxDB token and avoid untrusted content in the client.","tier":"B","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"businesses","plain_action":null,"pkeys":["awslabstimestreamforinfluxdbmcpserver"],"ptokens":["awslabs","for","influxdb","mcp","server","timestream"],"labels":["aitooling","aws","high","influxdb","labdisclosure","mcp","pypi","python","timestream"],"campaign_type":null,"search_a":"'-126681':18A,21A '-2026':17A,20A 'aw':13A 'awslabs.timestream':22A 'configur':9A 'connect':8A 'cve':16A,19A 'endpoint':5A 'for':24A 'for-influxdb-mcp-server':23A 'handl':10A 'improp':1A 'influxdb':25A 'intend':4A 'lab':14A 'mcp':26A 'restrict':2A 'server':27A 'timestream':15A","search_b":"'ai':29B 'ai-tool':28B 'api':74B 'attack':57B,80B 'aw':31B,40B 'configur':72B 'connect':53B 'control':81B 'craft':64B 'disclosur':35B 'endpoint':51B 'influxdb':32B,44B,65B,73B 'inject':60B 'lab':34B,41B 'lab-disclosur':33B 'mcp':36B,45B 'plant':62B 'prompt':59B 'python':37B 'remot':56B 'restrict':49B 'send':70B 'server':46B,69B,78B 'timestream':38B,42B 'token':75B 'tool':30B 'url':66B 'use':58B","search_c":"'-126681':84C,93C,174C,326C '-185':110C '-2026':83C,92C,173C,325C '0.0.12':232C '0.0.19':234C,249C '11/16/2026':121C '12':122C '2026':109C '2f9r':329C '30':123C 'acknowledg':332C 'actor':197C,227C 'address':240C 'affect':275C 'ai':156C 'also':278C 'amazon':159C 'api':221C,282C,305C 'assist':157C 'attent':118C 'avoid':312C 'aw':87C,90C,100C,111C,113C,128C 'aws-security@amazon.com':355C 'awslabs.timestream':135C,242C 'bulletin':85C,107C 'client':153C,211C,318C 'code':263C 'collabor':343C 'concern':362C 'configur':183C,219C,284C 'confirm':229C 'connect':182C,192C 'content':114C,322C 'context':146C,212C 'control':228C 'coordin':349C 'could':198C,215C 'craft':205C 'custom':271C 'cve':82C,91C,172C,324C 'data':169C 'date':120C 'deriv':262C 'descript':126C 'disclosur':351C 'ecur':359C 'email':354C 'endpoint':98C,190C,225C 'ensur':258C 'fix':270C,295C 'for-influxdb-mcp-serv':136C,243C 'forimoc':339C 'fork':260C 'fulli':294C 'g4f3':330C 'ghsa':328C 'ghsa-2f9r-g4f3-wc2j':327C 'handl':181C 'id':108C 'identifi':171C 'impact':230C 'import':116C 'improp':94C 'incorpor':267C 'influxdb':104C,132C,138C,162C,168C,206C,220C,245C,281C,304C 'inject':201C 'intend':97C 'introduc':203C 'invoke1442':341C 'issu':176C,237C,297C,346C 'lab':88C,101C,129C 'latest':255C 'least':309C 'let':151C 'like':335C 'manag':158C 'mcp':105C,133C,139C,148C,152C,210C,246C,317C 'model':145C 'need':311C 'new':269C 'open':143C 'patch':265C 'permiss':310C 'pleas':353C 'pm':124C 'process':320C,352C 'prompt':200C 'protocol':147C 'pst':125C 'public':119C 'question':360C 'read':165C 'recommend':251C 'refer':323C 'remot':195C 'requir':117C 'resolut':235C 'resourc':163C 'restrict':95C,188C 'rotat':279C 'scope':112C 'send':217C 'server':106C,134C,140C,149C,180C,185C,214C,247C,287C,315C 'sourc':144C 'thank':337C 'timestream':89C,102C,130C,160C 'token':222C,283C,306C 'type':115C 'unauthent':196C 'untrust':321C 'upgrad':252C,301C 'url':207C 'use':199C,273C,302C,313C 'version':231C,248C,256C,276C 'vulner':350C 'wc2j':331C 'workaround':288C,292C 'would':334C 'write':167C 'yuremin':338C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-16T00:00:00+00:00","kev":null,"cvss_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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"ff89ba41-3aa1-4d27-914a-91399e9639e5","poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/2026-185-aws/#CVE-2026-126681","url":"https://aws.amazon.com/security/security-bulletins/2026-185-aws/","severity":null,"published_at":"2026-11-16T00:00:00+00:00","modified_at":null,"first_seen_at":"2026-11-16T21:24:03+00:00","fetched_at":"2026-11-16T21:24:03+00:00","note":"AWS: CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS"},{"source":"nvd","external_id":"CVE-2026-126681","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-126681","severity":null,"published_at":"2026-11-16T21:17:25+00:00","modified_at":"2026-11-16T21:17:25+00:00","first_seen_at":"2026-11-16T21:38:58+00:00","fetched_at":"2026-11-16T21:38:59+00:00","note":null}],"documents":[{"id":172437,"url":"https://aws.amazon.com/security/security-bulletins/2026-185-aws/","title":"AWS: CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS","kind":"advisory","source":"lab","publisher":"research","text":"CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS\n\n### CVE-2026-126681 - Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server\n\nBulletin ID: 2026-185-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 11/16/2026 12:30 PM PST\n\n Description:\n\nThe AWS Labs Timestream for InfluxDB MCP Server (awslabs.timestream-for-influxdb-mcp-server) is an open source Model Context Protocol (MCP) server that lets MCP clients, such as AI assistants, manage Amazon Timestream for InfluxDB resources and read and write InfluxDB data. We identified CVE-2026-126681, an issue in how the server handles connection configuration. The server did not restrict which endpoints it connects to. A remote unauthenticated actor could use prompt injection to introduce a crafted InfluxDB URL into the MCP client context. The server could then send its configured InfluxDB API token to an endpoint the actor controls confirmation.\n\nImpacted versions: >=0.0.12 AND <0.0.19\n\nResolution:\n\nThis issue has been addressed in awslabs.timestream-for-influxdb-mcp-server version 0.0.19. We recommend upgrading to the latest version and ensuring any forked or derivative code is patched to incorporate the new fixes. Customers who used an affected version should also rotate any InfluxDB API tokens configured for the server.\n\nWorkarounds:\n\nThere is no workaround that fully fixes this issue. Until you can upgrade, use an InfluxDB API token with the least permissions needed. Avoid using the server with MCP clients that process untrusted content.\n\nReferences:\n\n- CVE-2026-126681\n- GHSA-2f9r-g4f3-wc2j\n\nAcknowledgement:\n\nWe would like to thank @Yuremin, @FORIMOC and @invoke1442 for collaborating on this issue through the coordinated vulnerability disclosure process.\n\n Please email aws-security@amazon.com with any s ecurity questions or concerns.","published_at":"2026-11-16T00:00:00+00:00","relation":"advisory","confidence":null,"note":null},{"id":172528,"url":"https://github.com/awslabs/mcp/security/advisories/GHSA-2f9r-g4f3-wc2j","title":"Vendor advisory: github.com","kind":"vendor","source":"nvd","publisher":"vendor","text":null,"published_at":"2026-11-16T20:40:49+00:00","relation":"advisory","confidence":null,"note":"Vendor advisory: github.com"},{"id":172580,"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-185-aws/","title":"AWS Security Bulletins: CVE-2026-126681 - Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server","kind":"vendor","source":"vendor","publisher":null,"text":"CVE-2026-126681 - Improper restriction of intended endpoints in AWS Labs Timestream for InfluxDB MCP Server\n\nBulletin ID: 2026-185-AWS Publication Date: 11/16/2026 12:30 PM PST 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. Impacted versions: >=0.0.12 AND <0.0.19 Refer to the article for the most up-to-date and complete information.","published_at":"2026-11-16T21:03:04+00:00","relation":"advisory","confidence":null,"note":"AWS Security Bulletins"}],"disclosures":[],"exploit_sources":[],"notice":"Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai"}