Live › vulnerability › CVE-2026-116109
Go to dashboardContinue 2.0.0 passes MCP server transport settings through MCPManagerSingleton.setConnections in core/config/ConfigHandler.ts without sanitizing them. A remote attacker who can supply that configuration can inject OS commands that run on the host.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 03:39 UTC. All times on this page are UTC.
Teams running Continue 2.0.0 with MCP servers configured, especially where the configuration can be influenced by a repository, a shared config, or a remote source. Installs without MCP server transports configured are likely not reachable through this path, but the sources do not confirm that. The sources say the vendor did not respond to disclosure, so no patch is confirmed.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Continue | vscode | 2.0.0 | – |
2.1.0-vscode pre-release notes mentions thisEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
A vulnerability has been found in continuedev Continue 2.0.0. This vulnerability affects the function MCPManagerSingleton.setConnections of the file core/config/ConfigHandler.ts of the component MCP Server Transport. Such manipulation leads to os command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
This page as .md · .json · in your agent: get_signal("CVE-2026-116109")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.