Skip to main content
← Vulnerabilities

MongoDB Atlas SQL ODBC Driver uses ignored SQLBindCol BufferLength as fixed-width row-array stride, causing out-of-bounds writes

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

2.1LowCNA
Exploited
No known exploitation
Fix
Fixed in 3.0.1
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.0.1.

5Pcve.now Index 5 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Data gap: No advisory context yet
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity2.1/10CVSS 2.1
  • No patch0/5No signal

What would change the score

  • Would score about 60 if added to CISA KEV
  • Would score about 55 if CISA's SSVC rates exploitation active
  • Would score about 24 if advisories confirm default setups are exposed

CVE-2026-120959 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.1 (low) and affects Atlas SQL; fixed in 3.0.1.

Published
Last modified
Published
Not listed in CISA KEV
5/100 · provisional
Fix
Fixed in 3.0.1
None on Exploit-DB, Metasploit or GitHub

Summary

The MongoDB Atlas SQL ODBC Driver, which client applications use to query MongoDB Atlas data, is affected. An attacker who can influence the values returned by a query may cause data to be written outside the memory buffer the application provided, potentially corrupting application memory or crashing the client process, though this only occurs when the application requests multiple result rows in a specific way.

Read the original description

A memory-handling flaw in the MongoDB Atlas SQL ODBC Driver can cause values returned for a query to be written outside the bounds of a buffer provided by the calling application. A party able to influence the values a query returns may cause data to be placed at an unintended location in the client application's memory, which may result in unintended modification of that memory or termination of the client process. Reaching this condition depends on a specific, application-chosen way of requesting several result rows at once.

What to do

  • Upgrade to a fixed version: 3.0.1.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • MongoDB Atlas SQL

    From 1.3.0 · fixed in 3.0.1

Evidence 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-120959

Is CVE-2026-120959 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-120959?

Atlas SQL: from 1.3.0 before 3.0.1.Source: cve.now feed data

How do I fix CVE-2026-120959?

Upgrade to a fixed version: 3.0.1.Source: cve.now feed data