{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-75573 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-75573 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-75573 is a medium-severity vulnerability in MongoDB BI Connector, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-75573 and fix it if it is affected.\n\nWhat it is: CVE-2026-75573 is a medium-severity vulnerability in MongoDB BI Connector, published on 27 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-75573 in the wild and no public exploit code.\n\nAffected product: MongoDB BI Connector. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-75573/ (Markdown: https://insights.sbomify.com/CVE-2026-75573/index.md)","id":"CVE-2026-75573","markdown":"https://insights.sbomify.com/CVE-2026-75573/index.md","name":"CVE-2026-75573","record":{"aliases":["GHSA-gq2v-frgg-2m9q"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"MongoDB BI Connector","requires_auth":"low_privilege","summary":"Local attackers can read TLS private-key passwords from logs when duplicate options are used, potentially accessing encrypted keys.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"bi_connector","vendor":"mongodb"}],"cvss":{"score":4.1,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"MongoDB Connector for BI mongodrdl Logs TLS Private-Key Password When Duplicate Options Are Supplied","id":"CVE-2026-75573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Grav before 4.2.2 Remote Code Execution via Email Twig","id":"CVE-2026-75574"},"packages":[],"prev":{"headline":"Mce-operator-bundle: all github actions pinned by mutable tag, not commit sha","id":"CVE-2026-75569"},"products":["BI Connector"],"published":"2026-08-27","related":[{"cvss_score":8.7,"headline":"MongoDB Connector for BI Improper Error Handling of Log Write Failures May Cause Loss of SQL Service","id":"CVE-2026-81517","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.7,"headline":"BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections","id":"CVE-2026-81518","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.7,"headline":"MongoDB Connector for BI Unbounded Authentication Negotiation Leading to Connection Exhaustion","id":"CVE-2026-81520","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.5,"headline":"MongoDB Connector for BI Unescaped Object Names in Generated SHOW CREATE Output","id":"CVE-2026-77586","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.3,"headline":"MongoDB Connector for BI Improper Error Handling During Schema Sampling May Cause Loss of SQL Service","id":"CVE-2026-81490","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.2,"headline":"MongoDB BI Connector Improper Memory Handling During Failed Kerberos Authentication May Cause Process Termination","id":"CVE-2026-75159","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":5.6,"headline":"MongoDB Connector for BI Incomplete Escaping of Stored Metadata in Generated SHOW CREATE Output","id":"CVE-2026-77184","kev_date_added":null,"published":"2026-08-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["MongoDB"]},"summary":"Local attackers can read TLS private-key passwords from logs when duplicate options are used, potentially accessing encrypted keys.","url":"https://insights.sbomify.com/CVE-2026-75573/"}