# CVE-2026-75573: MongoDB Connector for BI mongodrdl Logs TLS Private-Key Password When Duplicate Options Are Supplied

> Local attackers can read TLS private-key passwords from logs when duplicate options are used, potentially accessing encrypted keys.

- **Severity:** Medium 4.1 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-gq2v-frgg-2m9q

## What is CVE-2026-75573?

CVE-2026-75573 is a medium-severity vulnerability in MongoDB BI Connector, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In MongoDB Connector for BI, mongodrdl may write a TLS private-key password to standard error when the password is supplied through both the connection URI and the corresponding command-line option. A local user with access to the captured command output and encrypted key file may use the disclosed password to access the associated TLS client key.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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

It affects 1 product.


Products: Mongodb Bi Connector.

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

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

## Is CVE-2026-75573 being exploited?

There is no known exploitation of CVE-2026-75573 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-75573 and fix it if it is affected.

What it is: CVE-2026-75573 is a medium-severity vulnerability in MongoDB BI Connector, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-75573 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-75573/ (Markdown: https://insights.sbomify.com/CVE-2026-75573/index.md)
```

## Sources

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

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