An unauthenticated client that can reach a MongoDB Connector for BI deployment configured with Kerberos authentication may cause mongosqld to terminate when a crafted authentication exchange encounters a specific GSSAPI error-handling condition. This can interrupt BI Connector availability until the process restarts.
CVE-2026-75159
Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-08-27. a secondary CVSS source baseline 5.9; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(high)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 18%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 27, 2026Release 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-75159(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 12× in last 7d / 12× 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-30 01:22 UTCEPSS rescore
- 2026-08-29 21:08 UTCEG score recompute
- 2026-08-29 21:08 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 21:22 UTCGHSA enrichment
- 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
Related CVEs(same CWE)
Same CWE
10 shownCWE-415
- CVE-2007-4773EG 9.8CRITICAL
- CVE-2016-8619NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2016-8618NVD 5.3EG 9.8EPSS p91CRITICAL
- CVE-2015-9165EG 9.8CRITICAL
- CVE-2017-18201EG 9.8CRITICAL
- CVE-2017-18174EG 9.8CRITICAL
- CVE-2017-1000232EG 9.8CRITICAL
- CVE-2017-1000231EG 9.8CRITICAL
- CVE-2017-16820EG 9.8EPSS p90CRITICAL
- CVE-2017-14952EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-75159?
When was CVE-2026-75159 disclosed?
Is CVE-2026-75159 actively exploited?
What is the CVSS score of CVE-2026-75159?
How do I remediate CVE-2026-75159?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75159
Is Your Infrastructure Affected by CVE-2026-75159?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.