{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-19003 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-19003 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19003 is a high-severity memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 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-19003 and fix it if it is affected.\n\nWhat it is: CVE-2026-19003 is a high-severity memory corruption vulnerability in MongoDB BI Connector ODBC Driver, published on 12 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-19003 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-19003/ (Markdown: https://insights.sbomify.com/CVE-2026-19003/index.md)","id":"CVE-2026-19003","markdown":"https://insights.sbomify.com/CVE-2026-19003/index.md","name":"CVE-2026-19003","record":{"aliases":["GHSA-5vfq-q6f3-hh9v"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MongoDB BI Connector","requires_auth":"none","summary":"Attacker can trigger buffer overflow via oversized path settings in ODBC driver setup dialog, potentially leading to code execution or crash.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"bi_connector_odbc_driver","vendor":"mongodb"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A data source definition containing an over-length file path setting may cause the MongoDB BI Connector ODBC Driver setup dialog to write outside the bounds of an allocated buffer. The issue stems from an incorrect buffer capacity calculation in the dialog's file and folder selection handling, and is reached only when a user opens the setup dialog for such a data source and initiates a file or folder selection. Depending on build configuration, the result may range from abnormal process termination to, under certain conditions, execution of unintended code in the context of the user running the dialog.","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":"Memory corruption in BI Connector ODBC Driver","id":"CVE-2026-19003","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":"MongoDB BI Connector ODBC Driver Memory-Safety Issue When Handling Stored Procedure Output Parameters","id":"CVE-2026-19004"},"packages":[],"prev":{"headline":"Crafted database metadata may cause memory corruption in MongoDB BI Connector ODBC Driver","id":"CVE-2026-19002"},"products":["BI Connector ODBC Driver"],"published":"2026-08-12","related":[{"cvss_score":9.5,"headline":"MongoDB BI Connector ODBC driver may write outside an allocated buffer when handling oversized catalog object names","id":"CVE-2026-19001","kev_date_added":null,"published":"2026-08-12"},{"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":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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["MongoDB"]},"summary":"Attacker can trigger buffer overflow via oversized path settings in ODBC driver setup dialog, potentially leading to code execution or crash.","url":"https://insights.sbomify.com/CVE-2026-19003/"}