Skip to main content
EPSS 0.1%top 99%

CVE-2026-75573: CWE-532: Insertion of Sensitive Information into Log File in MongoDB BI Connector

0
Medium
VulnerabilityCVE-2026-75573cvecve-2026-75573cwe-532
Published: 08/27/2026 (08/27/2026, 16:01:55 UTC)
Source: CVE Database V5
Vendor/Project: MongoDB
Product: BI Connector

Description

CVE-2026-75573 is a medium severity vulnerability in MongoDB Connector for BI version 2.12.0 where the mongodrdl tool may write a TLS private-key password to standard error if the password is supplied both via the connection URI and command-line option. This disclosure could allow a local user with access to the command output and encrypted key file to obtain the password and access the TLS client key.

CVSS v4.0

Score 4.1medium

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
Low
User Interaction
Active
Vuln. Confidentiality
High
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
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

Affected software

MongoDB

BI Connector

Affected versions
>=2.12.0 <2.14.30

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/10/2026, 04:39:03 UTC

Technical Analysis

The vulnerability involves the mongodrdl component of MongoDB Connector for BI version 2.12.0 writing sensitive TLS private-key passwords to standard error output when the password is provided through both the connection URI and the command-line option. This leakage of sensitive information (CWE-532) could enable a local attacker with access to the command output and encrypted key file to retrieve the password and compromise the associated TLS client key.

Potential Impact

An attacker with local access to the system and the ability to capture the command output and access the encrypted TLS key file could obtain the TLS private-key password. This could lead to unauthorized use of the TLS client key, potentially undermining the confidentiality and integrity of TLS communications involving the BI Connector.

Mitigation Recommendations

No official patch or remediation level is currently documented for this vulnerability. Users should avoid supplying the TLS private-key password through both the connection URI and command-line option simultaneously to prevent password disclosure. Monitor the vendor advisory for updates regarding fixes or official mitigations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mongodb
Date Reserved
2026-08-17T22:00:14.773Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6a906badacd9273b49839ace

Added to database: 08/27/2026, 16:54:05 UTC

Last enriched: 09/10/2026, 04:39:03 UTC

Last updated: 10/10/2026, 06:48:19 UTC

Views: 39

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses