# CVE-2026-19502: Insufficient redaction of sensitive configuration values in diagnostic output of MongoDB SQL Schema Builder CLI

> Local attackers can read unredacted authentication credentials from MongoDB SQL Schema Builder CLI diagnostic logs or terminal output.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-wx8h-2jpv-xvwr, UBUNTU-CVE-2026-19502

## What is CVE-2026-19502?

CVE-2026-19502 is a medium-severity vulnerability in MongoDB Schema Builder CLI, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MongoDB SQL Schema Builder CLI records its startup configuration to standard output and, when file logging is enabled, to a log file on disk. Certain connection settings were written without redaction, so authentication material supplied by the operator could appear in plaintext in that diagnostic output. A local user with read access to the terminal session or the log directory, or anyone with access to a location where those logs are subsequently collected, could obtain those values.

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

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

It affects 1 product.


Products: Mongodb Sql Schema Builder Cli.

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

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

## Is CVE-2026-19502 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19502 is a medium-severity vulnerability in MongoDB Schema Builder CLI, published on 12 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19502 in the wild and no public exploit code.

Affected product: MongoDB Schema Builder CLI. 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-19502/ (Markdown: https://insights.sbomify.com/CVE-2026-19502/index.md)
```

## Sources

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

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