Skip to main content
VulnerabilityPublished

CVE-2026-19502: MongoDB Schema Builder CLI · Sensitive Data in Logs

Affects MongoDB Schema Builder CLISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.2.1 when convenient.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.2.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade MongoDB Schema Builder CLI to 1.2.1.

Affected software

ProductAffectedFixed in
MongoDBSchema Builder CLIAffected
  • >=1.0.0 <1.2.1
Fixed in
  • 1.2.1
npmmongodb-schema-builder-clipkg:npm/mongodb-schema-builder-cliOther threatsAffected
  • =1.0.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to terminal sessions and log directories to trusted users only. Avoid enabling file logging if possible or ensure logs are stored securely with strict access controls.

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.

References

Community reviews

Loading reviews…