{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-77586 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77586 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77586 is a high-severity SQL injection vulnerability in MongoDB BI Connector, published on 28 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-77586 and fix it if it is affected.\n\nWhat it is: CVE-2026-77586 is a high-severity SQL injection vulnerability in MongoDB BI Connector, published on 28 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-77586 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-77586/ (Markdown: https://insights.sbomify.com/CVE-2026-77586/index.md)","id":"CVE-2026-77586","markdown":"https://insights.sbomify.com/CVE-2026-77586/index.md","name":"CVE-2026-77586","record":{"aliases":["GHSA-7x84-hvm6-wgf7"],"analysis":{"component_type":"database","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"MongoDB BI Connector","requires_auth":"low_privilege","summary":"Attackers can inject SQL into generated DDL statements via unescaped object names, leading to code execution when the output is replayed.","user_interaction":"required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"bi_connector","vendor":"mongodb"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"In MongoDB Connector for BI, MongoDB object names such as collection, field, and index names are placed into the quoted identifiers of the DDL text returned by SHOW CREATE statements without escaping the identifier delimiter. A user with permission to write to a sampled MongoDB collection can choose a name that closes the quoted identifier early, so that additional SQL text becomes part of the generated output. If an operator or automated tool later replays that generated statement against a SQL server, the additional text is executed with the privileges of that session.","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 Unescaped Object Names in Generated SHOW CREATE Output","id":"CVE-2026-77586","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Tor","id":"CVE-2026-77587"},"packages":[],"prev":{"headline":"Improper Validation of SSH Target in Okta Privileged Access Client","id":"CVE-2026-77585"},"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":"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.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":"total"},"state":"PUBLISHED","updated":"2026-08-31","vendors":["MongoDB"]},"summary":"Attackers can inject SQL into generated DDL statements via unescaped object names, leading to code execution when the output is replayed.","url":"https://insights.sbomify.com/CVE-2026-77586/"}