# CVE-2026-120065: psqlODBC does not escape a server-supplied column name in its updatable-cursor queries


- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/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-120065, GHSA-9cg8-r57h-h6jj, GHSA-gv3c-v55x-3f23, UBUNTU-CVE-2026-120065

## What is CVE-2026-120065?

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

### Official description

For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC uses that column to identify rows. It places the column's name, as reported by the server, between double quotes in its keyset queries and in the WHERE clause of its positioned SELECT, UPDATE, and DELETE statements, without doubling any double quote in the name. A column name that contains a double quote therefore changes the SQL that the driver runs with the application's privileges, including which rows a positioned UPDATE or DELETE affects. Any database user who can create a table that the application reads with an updatable cursor can choose such a name, and so can a server not trusted under current SSL settings. Versions before psqlODBC 18.00.0006 are affected.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120065 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120065 is a high-severity vulnerability in PostgreSQL psqlODBC, published on 2 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120065 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-120065/ (Markdown: https://insights.sbomify.com/CVE-2026-120065/index.md)
```

## Sources

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

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