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

Published Aug 12, 2026
·
Updated

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.

Affected Software

1 affected component
MongoDB MongoDB SQL Schema Builder CLI

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    Ensure that local users with read access to the terminal session or the MongoDB SQL Schema Builder CLI log directory cannot access the diagnostic output and log files (e.g., restrict OS permissions and access to the log directory / locations where logs are collected).

  2. Operational

    After changing any operator-supplied authentication material that may have appeared in plaintext in MongoDB SQL Schema Builder CLI diagnostic output/log files, rotate those credentials to remove any exposed secrets.

Event History

Aug 12, 2026
CVE Published
via MITRE·08:14 PM
Data Sourced
via MITRE·08:14 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-19502?

The severity of CVE-2026-19502 is rated as medium with a score of 5.5.

2

What is CVE-2026-19502 about?

CVE-2026-19502 involves insufficient redaction of sensitive configuration values in the MongoDB SQL Schema Builder CLI's diagnostic output.

3

How do I fix CVE-2026-19502?

You can mitigate CVE-2026-19502 by ensuring that sensitive connection settings are not logged or are properly redacted in diagnostic outputs.

4

What impact does CVE-2026-19502 have on MongoDB users?

CVE-2026-19502 could expose authentication material in plaintext, potentially compromising user credentials.

5

Is there a workaround for CVE-2026-19502?

A workaround for CVE-2026-19502 is to disable file logging or adjust logging settings to prevent sensitive data from being recorded.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203