CVE-2026-120059: psqlODBC uses a server-supplied column name as a format string
PostgreSQL · psqlODBC
Vendor fix available · Affected: PostgreSQL psqlODBC · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 17% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- PostgreSQL · psqlODBCbefore 18.00.0006
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- PostgreSQL
- Published
- November 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-120059 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.