# CVE-2026-84967: Arbitrary command execution via shell-expanded connection string in Launch MongoDB Shell terminal

> Attackers can execute arbitrary commands on a developer's machine by tricking them into using a malicious connection string in the MongoDB VS Code extension.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** BIT-mongodb-2026-84967, GHSA-xc56-7hjg-wv9v

## What is CVE-2026-84967?

CVE-2026-84967 is a medium-severity command injection vulnerability in Mongodb Mongodb, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A component of the MongoDB extension for Visual Studio Code does not neutralize special characters in a connection string before that value is placed into a command line the extension composes for an integrated terminal. An unauthenticated remote unauthorized-user who persuades a developer to accept a user-supplied connection target, and then to open the extension's shell feature, can place characters of the unauthorized-user’s choosing into that command line. No privileges on the developer's machine are required, but several user actions are. The confirmation the developer sees does not display the supplied text.

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

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

1 open source package ship an affected version, including mongodb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mongodb` | Bitnami | From 1.13.0 | 1.17.1 |

Products: Mongodb Mongodb.

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

Upgrade mongodb to 1.17.1 or later.

## Is CVE-2026-84967 being exploited?

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

## Other vulnerabilities in Mongodb Mongodb

- [CVE-2025-14847](https://insights.sbomify.com/CVE-2025-14847/): MongoDB and MongoDB Server Improper Handling of Length Parameter Inconsistency (high 8.7, exploited in the wild)
- [CVE-2026-82067](https://insights.sbomify.com/CVE-2026-82067/): Auth bypass in MongoDB Server (critical 9.2)
- [CVE-2026-13072](https://insights.sbomify.com/CVE-2026-13072/): MongoDB Improper Input Validation in Compute Mode External Data Processing Leading to Memory Corruption (critical 9.2)
- [CVE-2017-15535](https://insights.sbomify.com/CVE-2017-15535/): Denial of service in n/a (critical 9.1)
- [CVE-2026-18691](https://insights.sbomify.com/CVE-2026-18691/): Improper Authentication in MongoDB Intra-Cluster Connections Allows Credential Exposure (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84967 is a medium-severity command injection vulnerability in Mongodb Mongodb, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-84967 in the wild and no public exploit code.

Affected packages and fixed versions:
- mongodb (Bitnami): affected from 1.13.0; fixed in 1.17.1

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-84967/ (Markdown: https://insights.sbomify.com/CVE-2026-84967/index.md)
```

## Sources

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

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