PatchSiren cyber security CVE debrief
CVE-2026-75159 MongoDB CVE debrief
CVE-2026-75159 is a high-severity vulnerability in MongoDB Connector for BI that can cause the mongosqld process to terminate when a crafted authentication exchange encounters a specific GSSAPI error-handling condition. This interruption affects BI Connector availability until the process restarts, particularly impacting deployments configured with Kerberos authentication. Defenders should assess their exposure and prioritize verifying the impact on their MongoDB Connector for BI deployments.
- Vendor
- MongoDB
- Product
- BI Connector
- CVSS
- HIGH 8.2
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-27
- Original CVE updated
- 2026-09-23
- Advisory published
- 2026-08-27
- Advisory updated
- 2026-09-23
Who should care
Defenders responsible for MongoDB Connector for BI deployments, especially those configured with Kerberos authentication, should assess their exposure and prioritize verifying the impact of this vulnerability.
Why it matters
CVE-2026-75159 is a high-severity vulnerability in MongoDB Connector for BI that can cause the mongosqld process to terminate, interrupting BI Connector availability. Defenders should prioritize verifying exposure and assessing the impact on their deployments, especially those configured with Kerberos authentication.
- Potential interruption of BI Connector availability
- Need to verify exposure and assess impact on MongoDB Connector for BI deployments
- Possible need to upgrade to version 2.14.30 or later
- Requirement to review Kerberos authentication settings
Technical summary
CVE-2026-75159 is a high-severity vulnerability in MongoDB Connector for BI that can cause the mongosqld process to terminate when a crafted authentication exchange encounters a specific GSSAPI error-handling condition. This can interrupt BI Connector availability until the process restarts. The vulnerability has a CVSS score of 8.2 and affects versions prior to 2.14.30. It is crucial for defenders to prioritize verifying exposure and assessing the impact on their MongoDB Connector for BI deployments, especially those configured with Kerberos authentication. Detailed technical analysis and verification of the vulnerability's impact are necessary to ensure the security of affected deployments.
Defensive priority
Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their MongoDB Connector for BI deployments, especially those configured with Kerberos authentication.
Recommended defensive actions
- Verify MongoDB Connector for BI version and configuration
- Assess exposure to unauthenticated client attacks
- Review Kerberos authentication settings
- Consider upgrading to version 2.14.30 or later
- Perform a thorough review of the current security posture
- Implement additional monitoring for potential attacks
- Document and track the verification process and findings
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the exact scope of affected deployments and potential impact require further verification.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-75159 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-75159
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-75159 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75159
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://www.mongodb.com/docs/bi-connector/current/release-notes/
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.