# CVE-2026-120952: An out-of-bounds write in the MongoDB Atlas SQL ODBC Driver may be triggered when a value of a particular database type is retrieved into a


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:H/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-v67f-82m7-4vcj

## What is CVE-2026-120952?

CVE-2026-120952 is a medium-severity vulnerability in MongoDB Atlas SQL ODBC Driver, published on 3 Nov 2026. 

### Official description

An out-of-bounds write in the MongoDB Atlas SQL ODBC Driver may be triggered when a value of a particular database type is retrieved into a fixed-width client-side target. The driver produces a textual form of the value that is longer than the fixed target the ODBC interface defines, and copies it without limiting the copy to the target's real size. A database user with basic write privileges can influence part of the data written outside the target, which may corrupt memory in the application using the driver and cause that application to terminate unexpectedly.

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

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


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

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

## Is CVE-2026-120952 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: MongoDB Atlas SQL ODBC Driver. 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-120952/ (Markdown: https://insights.sbomify.com/CVE-2026-120952/index.md)
```

## Sources

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

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