# CVE-2026-120959: 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 buff


- **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-g8hv-jrw6-9rw3

## What is CVE-2026-120959?

CVE-2026-120959 is a low-severity vulnerability in MongoDB Atlas SQL, published on 3 Nov 2026. 

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-120959?


## How do I fix CVE-2026-120959?

No fix has been published for CVE-2026-120959 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120959 being exploited?

There is no known exploitation of CVE-2026-120959 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120959 and fix it if it is affected.

What it is: CVE-2026-120959 is a low-severity vulnerability in MongoDB Atlas SQL, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120959 in the wild and no public exploit code.

Affected product: MongoDB Atlas SQL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120959/ (Markdown: https://insights.sbomify.com/CVE-2026-120959/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120959
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120959
- OSV: https://osv.dev/vulnerability/CVE-2026-120959

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120959/
Summaries are generated and may contain mistakes; the official description above is the record.
