PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-75573 MongoDB CVE debrief

CVE-2026-75573 debrief based on the supplied source corpus. The CVE record was published on 2026-08-27T17:19:59.120Z and has not been modified since then. This vulnerability affects MongoDB Connector for BI, particularly versions 2.12.0 up to 2.14.30. 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. Defenders and administrators should assess exposure and prioritize remediation to prevent potential unauthorized access to TLS client keys.

Vendor
MongoDB
Product
BI Connector
CVSS
MEDIUM 4.1
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 and administrators responsible for MongoDB Connector for BI installations, particularly those using versions 2.12.0 up to 2.14.30, should assess exposure and prioritize remediation to prevent potential unauthorized access to TLS client keys.

Why it matters

CVE-2026-75573 is a vulnerability in MongoDB Connector for BI that could allow local users to access TLS client keys. Defenders should prioritize verifying and remediating affected installations to prevent potential unauthorized access.

  • Potential unauthorized access to TLS client keys
  • Possible elevation of privileges for local users
  • Need for verification of MongoDB Connector for BI versions and configurations
  • Potential data breaches or unauthorized access to sensitive information

Technical summary

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. This could allow a local user with access to the captured command output and encrypted key file to use the disclosed password to access the associated TLS client key. The vulnerability affects MongoDB Connector for BI versions 2.12.0 up to 2.14.30. Defenders should prioritize verifying and remediating affected installations to prevent potential unauthorized access to TLS client keys.

Defensive priority

Defenders should prioritize verifying and remediating MongoDB Connector for BI installations, focusing on version 2.12.0 up to 2.14.30, to prevent potential unauthorized access to TLS client keys.

Recommended defensive actions

  • Verify MongoDB Connector for BI version and update to 2.14.30 or later if necessary
  • Review and restrict access to command output and encrypted key files
  • Implement additional monitoring for potential unauthorized access attempts
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability in MongoDB Connector for BI, where mongodrdl may write a TLS private-key password to standard error. 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.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-75573 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-75573

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-75573 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75573

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

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.