# CVE-2026-116109: continuedev Continue MCP Server Transport ConfigHandler.ts MCPManagerSingleton.setConnections os command injection


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-3cxv-6mgc-j7c4

## What is CVE-2026-116109?

CVE-2026-116109 is a medium-severity vulnerability in continuedev Continue, published on 26 Oct 2026. 

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-116109?


## How do I fix CVE-2026-116109?

No fix has been published for CVE-2026-116109 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116109 being exploited?

There is no known exploitation of CVE-2026-116109 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-116109 and fix it if it is affected.

What it is: CVE-2026-116109 is a medium-severity vulnerability in continuedev Continue, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116109 in the wild and no public exploit code.

Affected product: continuedev Continue. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-116109/ (Markdown: https://insights.sbomify.com/CVE-2026-116109/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-116109
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-116109
- OSV: https://osv.dev/vulnerability/CVE-2026-116109

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-116109/
Summaries are generated and may contain mistakes; the official description above is the record.