{"id":"GHSA-2f9r-g4f3-wc2j","kind":"vulnerability","aliases":["GHSA-2f9r-g4f3-wc2j"],"related":[],"title":"CVE-2026-126681 Bulletin for AWS Labs Timestream - AWS","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 does not restrict which endpoints it connects to. A remote unauthenticated attacker using prompt injection can make it send its configured InfluxDB API token to an endpoint the attacker controls.","severity":"high","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["ai-tooling","aws","influxdb","lab-disclosure","mcp","python"],"not_affected_if":["version-0.0.19-or-later"],"how_to_check":"- Check the installed version of `awslabs.timestream-for-influxdb-mcp-server`; affected versions are `>=0.0.12` and `<0.0.19`.\n- Look for the InfluxDB API token configured for the server and any MCP clients that process untrusted content.","fix":"- `awslabs.timestream-for-influxdb-mcp-server` `0.0.19`\n- Rotate any InfluxDB API tokens configured for the server after upgrading.","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:25:19+00:00","category":"ai-tooling","confidence":0.75,"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.","reach":"internet","title":"AWS Timestream for InfluxDB MCP Server: prompt injection leaks InfluxDB API token","impact":"high","summary":"The AWS Labs Timestream for InfluxDB MCP Server does not restrict which endpoints it connects to. A remote unauthenticated attacker using prompt injection can make it send its configured InfluxDB API token to an endpoint the attacker controls.","audience":"developers","category":"ai-tooling","nicknames":[],"who_cares":["mcp","aws","influxdb","python"],"confidence":0.75,"fix_status":"available","needs_auth":"no","worst_case":"InfluxDB API token sent to an attacker-controlled endpoint","analyst_note":"Confirm the package registry entry and whether the sources state any setup or user interaction needed for the prompt injection to succeed.","how_to_check":"- Check the installed version of `awslabs.timestream-for-influxdb-mcp-server`; affected versions are `>=0.0.12` and `<0.0.19`.\n- Look for the InfluxDB API token configured for the server and any MCP clients that process untrusted content.","plain_action":"","product_name":"","needs_analyst":true,"not_affected_if":["version-0.0.19-or-later"],"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, especially where MCP clients process untrusted content. Forked or derivative code must also be patched. The sources do not say whether managed hosting changes exposure.","user_interaction":"unknown","product_ecosystem":"","needs_special_setup":"unknown","severity_if_unknown":"high"},"cost_usd":0.000851,"input_tokens":5221,"output_tokens":658,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-126681':3A,70C,79C,160C,312C '-185':96C '-2026':2A,69C,78C,159C,311C '0.0.12':218C '0.0.19':220C,235C '11/16/2026':107C '12':108C '2026':95C '2f9r':12A,17A,315C '30':109C 'acknowledg':318C 'actor':183C,213C 'address':226C 'affect':261C 'ai':21B,142C 'ai-tool':20B 'also':264C 'amazon':145C 'api':60B,207C,268C,291C 'assist':143C 'attack':49B,66B 'attent':104C 'avoid':298C 'aw':6A,9A,23B,31B,73C,76C,86C,97C,99C,114C 'aws-security@amazon.com':341C 'awslabs.timestream':121C,228C 'bulletin':4A,71C,93C 'client':139C,197C,304C 'code':249C 'collabor':329C 'concern':348C 'configur':58B,169C,205C,270C 'confirm':215C 'connect':44B,168C,178C 'content':100C,308C 'context':132C,198C 'control':67B,214C 'coordin':335C 'could':184C,201C 'craft':191C 'custom':257C 'cve':1A,68C,77C,158C,310C 'data':155C 'date':106C 'deriv':248C 'descript':112C 'disclosur':27B,337C 'ecur':345C 'email':340C 'endpoint':42B,64B,84C,176C,211C 'ensur':244C 'fix':256C,281C 'for-influxdb-mcp-serv':122C,229C 'forimoc':325C 'fork':246C 'fulli':280C 'g4f3':13A,18A,316C 'ghsa':11A,16A,314C 'ghsa-2f9r-g4f3-wc2j':10A,15A,313C 'handl':167C 'id':94C 'identifi':157C 'impact':216C 'import':102C 'improp':80C 'incorpor':253C 'influxdb':24B,35B,59B,90C,118C,124C,148C,154C,192C,206C,231C,267C,290C 'inject':52B,187C 'intend':83C 'introduc':189C 'invoke1442':327C 'issu':162C,223C,283C,332C 'lab':7A,26B,32B,74C,87C,115C 'lab-disclosur':25B 'latest':241C 'least':295C 'let':137C 'like':321C 'make':54B 'manag':144C 'mcp':28B,36B,91C,119C,125C,134C,138C,196C,232C,303C 'model':131C 'need':297C 'new':255C 'open':129C 'patch':251C 'permiss':296C 'pleas':339C 'pm':110C 'process':306C,338C 'prompt':51B,186C 'protocol':133C 'pst':111C 'public':105C 'python':29B 'question':346C 'read':151C 'recommend':237C 'refer':309C 'remot':47B,181C 'requir':103C 'resolut':221C 'resourc':149C 'restrict':40B,81C,174C 'rotat':265C 'scope':98C 'send':56B,203C 'server':37B,92C,120C,126C,135C,166C,171C,200C,233C,273C,301C 'sourc':130C 'thank':323C 'timestream':8A,33B,75C,88C,116C,146C 'token':61B,208C,269C,292C 'tool':22B 'type':101C 'unauthent':48B,182C 'untrust':307C 'upgrad':238C,287C 'url':193C 'use':50B,185C,259C,288C,299C 'version':217C,234C,242C,262C 'vulner':336C 'wc2j':14A,19A,317C 'workaround':274C,278C 'would':320C 'write':153C 'yuremin':324C","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, especially where MCP clients process untrusted content. Forked or derivative code must also be patched. The sources do not say whether managed hosting changes exposure.","tier":"B","verified":{},"analyst_revisit_at":null,"fix_status":"available","audience":"developers","plain_action":null,"pkeys":[],"ptokens":[],"labels":["aitooling","aws","high","influxdb","labdisclosure","mcp","python"],"campaign_type":null,"search_a":"'-126681':3A '-2026':2A '2f9r':12A,17A 'aw':6A,9A 'bulletin':4A 'cve':1A 'g4f3':13A,18A 'ghsa':11A,16A 'ghsa-2f9r-g4f3-wc2j':10A,15A 'lab':7A 'timestream':8A 'wc2j':14A,19A","search_b":"'ai':21B 'ai-tool':20B 'api':60B 'attack':49B,66B 'aw':23B,31B 'configur':58B 'connect':44B 'control':67B 'disclosur':27B 'endpoint':42B,64B 'influxdb':24B,35B,59B 'inject':52B 'lab':26B,32B 'lab-disclosur':25B 'make':54B 'mcp':28B,36B 'prompt':51B 'python':29B 'remot':47B 'restrict':40B 'send':56B 'server':37B 'timestream':33B 'token':61B 'tool':22B 'unauthent':48B 'use':50B","search_c":"'-126681':70C,79C,160C,312C '-185':96C '-2026':69C,78C,159C,311C '0.0.12':218C '0.0.19':220C,235C '11/16/2026':107C '12':108C '2026':95C '2f9r':315C '30':109C 'acknowledg':318C 'actor':183C,213C 'address':226C 'affect':261C 'ai':142C 'also':264C 'amazon':145C 'api':207C,268C,291C 'assist':143C 'attent':104C 'avoid':298C 'aw':73C,76C,86C,97C,99C,114C 'aws-security@amazon.com':341C 'awslabs.timestream':121C,228C 'bulletin':71C,93C 'client':139C,197C,304C 'code':249C 'collabor':329C 'concern':348C 'configur':169C,205C,270C 'confirm':215C 'connect':168C,178C 'content':100C,308C 'context':132C,198C 'control':214C 'coordin':335C 'could':184C,201C 'craft':191C 'custom':257C 'cve':68C,77C,158C,310C 'data':155C 'date':106C 'deriv':248C 'descript':112C 'disclosur':337C 'ecur':345C 'email':340C 'endpoint':84C,176C,211C 'ensur':244C 'fix':256C,281C 'for-influxdb-mcp-serv':122C,229C 'forimoc':325C 'fork':246C 'fulli':280C 'g4f3':316C 'ghsa':314C 'ghsa-2f9r-g4f3-wc2j':313C 'handl':167C 'id':94C 'identifi':157C 'impact':216C 'import':102C 'improp':80C 'incorpor':253C 'influxdb':90C,118C,124C,148C,154C,192C,206C,231C,267C,290C 'inject':187C 'intend':83C 'introduc':189C 'invoke1442':327C 'issu':162C,223C,283C,332C 'lab':74C,87C,115C 'latest':241C 'least':295C 'let':137C 'like':321C 'manag':144C 'mcp':91C,119C,125C,134C,138C,196C,232C,303C 'model':131C 'need':297C 'new':255C 'open':129C 'patch':251C 'permiss':296C 'pleas':339C 'pm':110C 'process':306C,338C 'prompt':186C 'protocol':133C 'pst':111C 'public':105C 'question':346C 'read':151C 'recommend':237C 'refer':309C 'remot':181C 'requir':103C 'resolut':221C 'resourc':149C 'restrict':81C,174C 'rotat':265C 'scope':98C 'send':203C 'server':92C,120C,126C,135C,166C,171C,200C,233C,273C,301C 'sourc':130C 'thank':323C 'timestream':75C,88C,116C,146C 'token':208C,269C,292C 'type':101C 'unauthent':182C 'untrust':307C 'upgrad':238C,287C 'url':193C 'use':185C,259C,288C,299C 'version':217C,234C,242C,262C 'vulner':336C 'wc2j':317C 'workaround':274C,278C 'would':320C 'write':153C 'yuremin':324C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-16T00:00:00+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"lab","external_id":"https://aws.amazon.com/security/security-bulletins/2026-185-aws/#GHSA-2f9r-g4f3-wc2j","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"}],"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}],"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"}