LiveActive security incident?Get immediate response
CVE Record

CVE-2026-19001: MongoDB BI Connector ODBC driver may write outside an allocated buffer when handling oversized catalog object names

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A specially oversized database catalog, schema, or object name can corrupt memory in an application using the MongoDB BI Connector ODBC Driver. The application may crash and, in some conditions, attacker-controlled code could run with that application's permissions, threatening confidentiality, integrity, and availability.

Executive priority

Treat confirmed version 1.0.0 deployments as urgent because compromise could affect application data and availability. Prioritize internet-facing or untrusted-input applications first. The absence of reported exploitation lowers immediate evidence of attack, but does not offset the critical technical impact.

Technical view

CVE-2026-19001 is an out-of-bounds write involving a fixed-size buffer during ODBC metadata retrieval. The supplied CVSS 3.1 score is 9.8: network-accessible, low complexity, no privileges, and no user interaction. The source bundle identifies version 1.0.0 as affected and lists CWE-190, while describing memory corruption and possible arbitrary code execution.

Likely exposure

Exposure requires the MongoDB BI Connector ODBC Driver, specifically the listed 1.0.0 version, and an application path where oversized metadata names can reach affected retrieval functions. The bundle marks other versions unaffected by default, but asset owners should verify exact installed versions and application data flows.

Exploitation context

The CVSS vector indicates remote exploitation may be possible without credentials or user interaction. However, the source bundle provides no proof of concept, observed attacks, or confirmed exploitation, and the CVE is not listed as KEV. Treat code execution as potential rather than demonstrated.

Researcher notes

The evidence is limited to the CVE record, CVE List data, and a referenced GitHub release. The bundle does not explicitly state that release 1.4.9 fixes this CVE, so remediation claims require vendor confirmation. The CWE-190 classification should be interpreted alongside the supplied out-of-bounds-write description.

Mitigation direction

  • Inventory applications and hosts using the MongoDB BI Connector ODBC Driver.
  • Prioritize removal or isolation of confirmed version 1.0.0 deployments.
  • Check MongoDB's release guidance to confirm the version containing the official correction.
  • Upgrade according to verified vendor guidance and normal change-control procedures.
  • Restrict untrusted input from reaching ODBC metadata retrieval paths where feasible.

Validation and detection

  • Confirm the installed ODBC driver version on every relevant application host.
  • Identify whether applications expose metadata retrieval operations to untrusted or remote inputs.
  • Review crash, memory-corruption, and abnormal-process logs around ODBC metadata activity.
  • After remediation, verify the vulnerable driver version is absent from deployment inventories.
  • Monitor MongoDB and CVE sources for clarified affected versions and remediation details.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-19001 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9mongodb
9.5CVSS 4.0CriticalCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N——mongodb

Vulnerability scoring details

Base CVSS 4.0 score

9.5Critical
CVSS 4.0 vector shape for CVE-2026-19001Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MongoDBBI Connector ODBC Driver1.0.0unaffected
Weakness

CWE details

CWE-190

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs