In MongoDB Connector for BI, mongodrdl may write a TLS private-key password to standard error when the password is supplied through both the connection URI and the corresponding command-line option. A local user with access to the captured command output and encrypted key file may use the disclosed password to access the associated TLS client key.
CVE-2026-75573
MEDIUMPre-NVD 4.44.4—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 4.4 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 4.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 4.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.4
- EG Score
- 4.4(high)
- EG Risk
- 20(Track)EG Risk 20/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity44% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 27, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026No patch confirmed yet.
generic
Release Notes for MongoDB Connector for BI - BI Connector - MongoDB Docs
https://www.mongodb.com/docs/bi-connector/current/release-notes/#mongodb-connector-for-bi-2.14.30Vendor Advisories for CVE-2026-75573(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-27 20:27 UTCEG score recompute
- 2026-08-27 20:27 UTCGHSA enrichment
- 2026-08-27 20:17 UTCEG score recompute
- 2026-08-27 20:17 UTCGHSA enrichment
- 2026-08-27 17:24 UTCEG score recompute
- 2026-08-27 16:46 UTCEG score recompute
- 2026-08-27 16:43 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-75573?
CVE-2026-75573 is a medium vulnerability published on August 27, 2026. In MongoDB Connector for BI, mongodrdl may write a TLS private-key password to standard error when the password is supplied through both the connection URI and the corresponding command-line option. A local user with access to the captured command output and encrypted key file may use the disclosed…
When was CVE-2026-75573 disclosed?
CVE-2026-75573 was first published in the National Vulnerability Database on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-75573?
CVE-2026-75573 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-75573?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-75573, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75573
Is Your Infrastructure Affected by CVE-2026-75573?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.