# CVE-2026-120059: psqlODBC uses a server-supplied column name as a format string


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/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-120059, GHSA-44rq-72jh-x2h8, GHSA-p6rq-g598-qx9f, UBUNTU-CVE-2026-120059

## What is CVE-2026-120059?

CVE-2026-120059 is a medium-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 places that column's name, as reported by the server, into a printf-style format string. It later expands that string with one argument while it builds the WHERE clause of its positioned SELECT, UPDATE, and DELETE statements. A column name that contains format directives makes the driver read unrelated memory, which can crash the application or copy client memory into query text sent to the server. The name can come from a server not trusted under current SSL settings, or from any database user who can create a table that the application reads with an updatable cursor. Versions before psqlODBC 18.00.0006 are affected.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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


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

Upgrade to a fixed version.

## Is CVE-2026-120059 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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