{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-19001 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-19001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19001 is a critical memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 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-19001 and fix it if it is affected.\n\nWhat it is: CVE-2026-19001 is a critical memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 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-19001 in the wild and no public exploit code.\n\nAffected product: MongoDB BI Connector ODBC Driver. 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-19001/ (Markdown: https://insights.sbomify.com/CVE-2026-19001/index.md)","id":"CVE-2026-19001","markdown":"https://insights.sbomify.com/CVE-2026-19001/index.md","name":"CVE-2026-19001","record":{"aliases":["GHSA-qp3w-mm2v-5347"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"MongoDB BI Connector","requires_auth":"none","summary":"An attacker can trigger memory corruption and potential code execution by supplying oversized catalog object names to the MongoDB BI Connector ODBC driver.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"bi_connector_odbc_driver","vendor":"mongodb"}],"cvss":{"score":9.5,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"The MongoDB BI Connector ODBC Driver may write outside the bounds of a fixed-size buffer when an application supplies an unusually long catalog, schema, or object name to a metadata retrieval function. This may result in memory corruption within the calling application's process, leading to abnormal termination and, under certain conditions, the potential for arbitrary code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"MongoDB BI Connector ODBC driver may write outside an allocated buffer when handling oversized catalog object names","id":"CVE-2026-19001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver","id":"CVE-2026-19002"},"packages":[],"prev":{"headline":"JeecgBoot Anonymous Chat Attachment send server-side request forgery","id":"CVE-2026-19000"},"products":["BI Connector ODBC Driver"],"published":"2026-08-12","related":[{"cvss_score":8.8,"headline":"Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver","id":"CVE-2026-19002","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":8.8,"headline":"MongoDB BI Connector ODBC Driver Memory-Safety Issue When Handling Stored Procedure Output Parameters","id":"CVE-2026-19004","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":8.7,"headline":"BI Connector ODBC Driver Improper Bounds Checking on Cursor Name Leading to Memory Corruption","id":"CVE-2026-81532","kev_date_added":null,"published":"2026-08-28"},{"cvss_score":8.4,"headline":"Memory corruption in BI Connector ODBC Driver","id":"CVE-2026-19003","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":7.1,"headline":"Memory corruption in BI Connector ODBC Driver","id":"CVE-2026-18888","kev_date_added":null,"published":"2026-08-12"},{"cvss_score":6,"headline":"MongoDB BI Connector ODBC Driver Memory-Safety Issue When Parsing Oversized LIMIT Values","id":"CVE-2026-81533","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":"total"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["MongoDB"]},"summary":"An attacker can trigger memory corruption and potential code execution by supplying oversized catalog object names to the MongoDB BI Connector ODBC driver.","url":"https://insights.sbomify.com/CVE-2026-19001/"}