# CVE-2026-120064: psqlODBC does not validate column numbers and row indexes in binding and descriptor functions


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120064, GHSA-7pq2-q7mj-ph8c, GHSA-vxfm-r3mv-m2fh, UBUNTU-CVE-2026-120064

## What is CVE-2026-120064?

CVE-2026-120064 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 

### Official description

Several psqlODBC entry points use an application-supplied column number or row index as an array index without validating it. SQLBindCol with a column number above 32767 wraps the binding count negative and a later copy runs off the array. A negative SQL_DESC_COUNT on an application row descriptor unbinds columns at negative indexes. SQLColAttribute with a very large column number uses a negative index. SQLSetPos(SQL_ADD) does not check the row number against the rowset size. An application that forwards untrusted column or row numbers exposes its process to out-of-bounds reads and writes. Versions before psqlODBC 18.00.0006 are affected.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-129 (Improper Validation of Array Index)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120064 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120064 in the wild and no public exploit code.

Affected product: PostgreSQL psqlODBC. 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-120064/ (Markdown: https://insights.sbomify.com/CVE-2026-120064/index.md)
```

## Sources

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

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