{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-81518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81518 is a high-severity authentication bypass vulnerability in MongoDB BI Connector, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81518 and fix it if it is affected.\n\nWhat it is: CVE-2026-81518 is a high-severity authentication bypass vulnerability in MongoDB BI Connector, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-81518 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-81518/ (Markdown: https://insights.sbomify.com/CVE-2026-81518/index.md)","id":"CVE-2026-81518","markdown":"https://insights.sbomify.com/CVE-2026-81518/index.md","name":"CVE-2026-81518","record":{"aliases":["GHSA-2r33-wv3m-hvxf"],"analysis":{"component_type":"database","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"MongoDB BI Connector","requires_auth":"none","summary":"Remote attackers can bypass client certificate authentication to read MongoDB data when the connector is configured with optional certificate verification.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"bi_connector","vendor":"mongodb"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"When mongosqld is configured with a client certificate authority file, the listener requests a client certificate during the TLS handshake but does not require one, so a client that presents no certificate is still accepted. In deployments that rely on client certificates as the sole means of identifying users, a remote party with network access to the listener can therefore establish a session and read the MongoDB data exposed through the connector.","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":"BI Connector Optional Client Certificate Verification Allows Unauthenticated Connections","id":"CVE-2026-81518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"MongoDB Connector for BI Unbounded Authentication Negotiation Leading to Connection Exhaustion","id":"CVE-2026-81520"},"packages":[],"prev":{"headline":"MongoDB Connector for BI Improper Error Handling of Log Write Failures May Cause Loss of SQL Service","id":"CVE-2026-81517"},"products":["BI Connector"],"published":"2026-08-28","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":"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["MongoDB"]},"summary":"Remote attackers can bypass client certificate authentication to read MongoDB data when the connector is configured with optional certificate verification.","url":"https://insights.sbomify.com/CVE-2026-81518/"}