# CVE-2026-77184: MongoDB Connector for BI Incomplete Escaping of Stored Metadata in Generated SHOW CREATE Output

> Attackers with schema modification rights can inject SQL into generated DDL, leading to code execution when the output is replayed by operators or tools.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-67f8-9r65-xc46

## What is CVE-2026-77184?

CVE-2026-77184 is a medium-severity SQL injection vulnerability in MongoDB BI Connector, published on 28 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

In MongoDB Connector for BI, the description text of a collection's JSON schema validator is incorporated into the comment text of the DDL returned by SHOW CREATE statements without complete escaping of backslash characters. A user with permission to modify a collection's schema validator, in deployments configured to build their SQL schema from those validators, can cause additional SQL text to be embedded in that generated output. If an operator or automated tool later replays that generated statement against a SQL server, the additional text is executed with the privileges of that session.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Mongodb Bi Connector.

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

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

## Is CVE-2026-77184 being exploited?

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

## Other vulnerabilities in MongoDB BI Connector

- [CVE-2026-81517](https://insights.sbomify.com/CVE-2026-81517/): MongoDB Connector for BI Improper Error Handling of Log Write Failures May Cause Loss of SQL Service (high 8.7)
- [CVE-2026-81518](https://insights.sbomify.com/CVE-2026-81518/): BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections (high 8.7)
- [CVE-2026-81520](https://insights.sbomify.com/CVE-2026-81520/): MongoDB Connector for BI Unbounded Authentication Negotiation Leading to Connection Exhaustion (high 8.7)
- [CVE-2026-77586](https://insights.sbomify.com/CVE-2026-77586/): MongoDB Connector for BI Unescaped Object Names in Generated SHOW CREATE Output (high 8.5)
- [CVE-2026-81490](https://insights.sbomify.com/CVE-2026-81490/): MongoDB Connector for BI Improper Error Handling During Schema Sampling May Cause Loss of SQL Service (high 8.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77184 is a medium-severity SQL injection vulnerability in MongoDB BI Connector, published on 28 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-77184 in the wild and no public exploit code.

Affected product: MongoDB BI Connector. 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-77184/ (Markdown: https://insights.sbomify.com/CVE-2026-77184/index.md)
```

## Sources

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

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