psqlODBC vulnerabilities and CVEs

Known vulnerabilities affecting psqlODBC, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.

11 vulnerabilities tracked.

• 7.5 Several psqlODBC entry points use an application-supplied column number or row index as an array index without validating it. CVE-2026-120064 2 Nov 2026
• 7.5 SQLSpecialColumns in psqlODBC splices the table and schema names it receives into its catalog query without escaping them, while the other… CVE-2026-120062 2 Nov 2026
• 7.5 The psqlODBC parser for ODBC escape sequences in application SQL text writes the argument offsets of a {fn} escape into a fixed 16-entry… CVE-2026-120061 2 Nov 2026
• 7.5 psqlODBC sizes its row cache from the column count of a cursor's first result, but recomputes the column count from each later FETCH reply… CVE-2026-120058 2 Nov 2026
• 7.5 psqlODBC copies the reply to a large-object read (loread) into the application's buffer using the length sent by the server, without… CVE-2026-120057 2 Nov 2026
• 7.1 For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC uses that column to identify rows. CVE-2026-120065 2 Nov 2026
• 6.8 For an updatable cursor over a table without OIDs that has an auto-increment int4 column, psqlODBC places that column's name, as reported… CVE-2026-120059 2 Nov 2026
• 5.9 For updatable cursors, which are enabled by default, psqlODBC adds hidden ctid and, for tables with OIDs, oid columns to the query. CVE-2026-120067 2 Nov 2026
• 5.9 When psqlODBC quotes a schema or table name into a 128-byte stack buffer, its length check lets it write up to two bytes past the end of… CVE-2026-120063 2 Nov 2026
• 5.9 psqlODBC trusts counts and lengths in server data in three places. CVE-2026-120060 2 Nov 2026
• 5.3 On Unix-like systems, when logging is enabled, psqlODBC creates its log files in /tmp by default, named from the program name, user name,… CVE-2026-120066 2 Nov 2026