CVE-2026-120059
psqlODBC uses a server-supplied column name as a format string
- Medium 6.8
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.
Key facts
- Published
- 2 Nov 2026
- Last changed
- 2 Nov 2026
- Assigned by
- PostgreSQL
- EPSS
- 0.261% likely to be exploited in the next 30 days, higher than 17.964% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 6.8CVSS 3.1, Mediumfrom the CNA (PostgreSQL)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:H
What to do
- Upgrade to psqlODBC 18.00.0006 or later. Each percent sign in the server-supplied column name is doubled before the name is placed in the format string.CNA solution statement
- Set UpdatableCursors=0 in the connection string or DSN, or use read-only cursors (SQL_CONCUR_READ_ONLY).CNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| PostgreSQL | psqlODBC |
|
Timeline
- 2 Nov 2026 Published