Skip to content
OpenAdvisories
High SUSE-SU-2026:5191-1 12 CVEs

Security update for psqlODBC

Published Nov 11, 2026 · Updated Nov 12, 2026

Summary

This update for psqlODBC fixes the following issues:

- CVE-2026-109448: denial of service via integer wraparound in SQLBindParameter (bsc#1285073).
- CVE-2026-120057: large-object read overflows the application buffer (bsc#1289252).
- CVE-2026-120058: row cache overflow when a later FETCH changes the column count (bsc#1289253).
- CVE-2026-120059: driver uses a server-supplied column name as a format string (bsc#1289254).
- CVE-2026-120060: driver does not validate server-supplied counts and lengths (bsc#1289255).
- CVE-2026-120061: ODBC escape parser stack buffer overflow (bsc#1289256).
- CVE-2026-120062: SQL injection through SQLSpecialColumns table and schema names (bsc#1289257).
- CVE-2026-120063: stack buffer overflow when quoting long schema and table names (bsc#1289258).
- CVE-2026-120064: driver does not validate column numbers and row indexes in binding and descriptor functions
(bsc#1289259).
- CVE-2026-120065: driver does not escape a server-supplied column name in its updatable-cursor queries (bsc#1289260).
- CVE-2026-120066: log files are created with default permissions at a predictable path and follow symbolic links
(bsc#1289261).
- CVE-2026-120067: stack buffer overflow when reading the keyset (ctid/oid) columns of an updatable cursor
(bsc#1289262).

Changes for psqlODBC:

- Update to 18.00.0006:
* https://odbc.postgresql.org/docs/release.html
* Hardening: SQLSetDescRecW stored a freed buffer and the address
of a local variable as deferred bound data. It now stores the
application's pointers, as SQLSetDescRec does.
* Hardening: SQLColumns returned uninitialized relkind and table
OID values when the table query returned no rows.
* Hardening: convert_linefeeds could dereference a NULL pointer
in one build configuration.
* Hardening: secure_sscanf limits an over-wide %Ns width,
msgtowstr checks for a zero buffer length, and the MSDTC
connect-string append is bounded.
- Update to 18.00.0005:
* https://odbc.postgresql.org/docs/release.html
* Fix the placeholder cast being truncated from parameter 1000
on, which failed with 'type 'timestam' does not exist'.
* Report the largest column size instead of SQL_NO_TOTAL (-4) as
COLUMN_SIZE for bytea in SQLGetTypeInfo, which broke bytea
parameters through MSDASQL.
- Update to 18.00.0004:
* Fix the result-conversions regression test on big-endian
systems.
- Update to 18.00.0003:
* Report SQLSTATE 22003 for out-of-range integer conversions
instead of silently returning the wrapped low bits.
* Fix statement level rollback (Protocol=7.4-2) discarding the
whole transaction on a syntax error.
* Do not wrap internal queries in a savepoint at
rollback-on-error level 0 (Protocol=7.4-0), which lost
transactions on servers without SAVEPOINT support.
* Redact the database password (ODBC PWD and libpq pqopt
password) in debug logs.
* Fix hang on COPY ... FROM STDIN / TO STDOUT: report it as
unsupported and keep the connection usable.
* Fix 'infinity'/'-infinity' dates being silently returned as
today's date.
* Document the connection string escaping rules.
- Update to 18.00.0002:
* Use a signed type for the error status.
* Redact sensitive connection parameters in the driver logs.
* Fix double free / heap corruption during SQLDisconnect
cleanup.
* Clear PGresults from per-query rollback.
* Validate UTF-16 surrogate pairs before combining them.
* Pass SQLSetDescRec field values correctly.
* Avoid reading before leading string literals.
* Detach freed application descriptors from statements.
* Reject invalid SQLPutData lengths.
* Reject overlong cursor names.
* Fix version reporting.
* Handle ARD bookmark allocation failure.
* Validate percent escapes before decoding connection string
values.
* Avoid reading past the end of conn_settings.
* Fix stack buffer overflow in getPrecisionPart().
* Fix SQLPrimaryKeys to exclude INCLUDE columns from the result.
- Update to 18.00.0000, 18.00.0001 and 17.00.0010:
* No code changes from 17.00.0009.
- Update to 17.00.0009:
* Fix the test suite for PostgreSQL 19, where
standard_conforming_strings is always on.
* Upgrade the GitHub Actions workflow: use prebuilt PostgreSQL
binaries, parallel matrix builds and a separate release job.
- Update to 17.00.0008:
* https://odbc.postgresql.org/docs/release.html
- fix build for SLE-15 by forcing gcc 14

Fixed packages 3

ReleasePackageFixed in
SUSE · SLES 15 SP7 Linux Enterprise Module for Basesystem 15 SP7 psqlODBC 18.00.0006-150600.3.5.1
SUSE · SLES 15 SP6 Linux Enterprise Server 15 SP6-LTSS psqlODBC 18.00.0006-150600.3.5.1
SUSE · SLES for SAP 15 SP6 Linux Enterprise Server for SAP Applications 15 SP6 psqlODBC 18.00.0006-150600.3.5.1

Vulnerabilities 12

  • High 7.5

    psqlODBC large-object read overflows the application buffer

    psqlODBC copies the reply to a large-object read (loread) into the application's buffer using the length sent by the server, without comparing it to the buffer size. A server not trusted under current SSL settings, or a man-in-the-middle, can return more byte…

  • High 7.5

    psqlODBC row cache overflow when a later FETCH changes the column count

    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 without checking that it matches. A server not trusted under current SSL settings can answer a later FETCH with more col…

  • High 7.5

    psqlODBC ODBC escape parser stack buffer overflow

    The psqlODBC parser for ODBC escape sequences in application SQL text writes the argument offsets of a {fn} escape into a fixed 16-entry stack array without a bound and does not initialize the array. An escape with too many arguments overflows the stack, and …

  • High 7.5

    psqlODBC SQL injection through SQLSpecialColumns table and schema names

    SQLSpecialColumns in psqlODBC splices the table and schema names it receives into its catalog query without escaping them, while the other catalog functions escape them. An application that passes an untrusted table or schema name to SQLSpecialColumns lets th…

  • High 7.5

    psqlODBC does not validate column numbers and row indexes in binding and descriptor functions

    Several psqlODBC entry points use an application-supplied column number or row index as an array index without validating it. SQLBindCol with a column number above 32767 wraps the binding count negative and a later copy runs off the array. A negative SQL_DESC…

  • High 7.1

    psqlODBC does not escape a server-supplied column name in its updatable-cursor queries

    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 o…

  • Medium 6.8

    psqlODBC uses a server-supplied column name as a format string

    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 WHER…

  • Medium 5.9

    psqlODBC SQLBindParameter heap memory corruption when binding more than 32767 parameters

    Integer wraparound in psqlODBC SQLBindParameter allows an application, or an attacker who controls how many parameters the application binds on one statement, to corrupt heap memory. psqlODBC stores the binding count in a signed 16-bit field. Binding paramete…

  • Medium 5.9

    psqlODBC does not validate server-supplied counts and lengths

    psqlODBC trusts counts and lengths in server data in three places. SQLBulkOperations uses a server-supplied row count in a size subtraction that can underflow. SQLStatistics iterates index keys using a server-supplied key count without bounding it to the fixe…

  • Medium 5.9

    psqlODBC stack buffer overflow when quoting long schema and table names

    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 the buffer for a long name. The names come from the application's SQL text: the table of a statement the driver parses to …

  • Medium 5.9

    psqlODBC stack buffer overflow copying ctid and oid values for updatable cursors

    For updatable cursors, which are enabled by default, psqlODBC adds hidden ctid and, for tables with OIDs, oid columns to the query. It copies each value into a 32-byte stack buffer using the length the server sent, without checking it against the buffer size,…

  • Medium 5.3

    psqlODBC log files are created with default permissions at a predictable path and follow symbolic links

    On Unix-like systems, when logging is enabled, psqlODBC creates its log files in /tmp by default, named from the program name, user name, and process ID, with the default permissions, typically world-readable, and follows symbolic links when opening them. A l…

References

  • report
    https://bugzilla.suse.com/1285073
  • report
    https://bugzilla.suse.com/1289252
  • report
    https://bugzilla.suse.com/1289253
  • report
    https://bugzilla.suse.com/1289254
  • report
    https://bugzilla.suse.com/1289255
  • report
    https://bugzilla.suse.com/1289256
  • report
    https://bugzilla.suse.com/1289257
  • report
    https://bugzilla.suse.com/1289258
  • report
    https://bugzilla.suse.com/1289259
  • report
    https://bugzilla.suse.com/1289260
  • report
    https://bugzilla.suse.com/1289261
  • report
    https://bugzilla.suse.com/1289262
  • web
    https://www.suse.com/security/cve/CVE-2026-109448
  • web
    https://www.suse.com/security/cve/CVE-2026-120057
  • web
    https://www.suse.com/security/cve/CVE-2026-120058
  • web
    https://www.suse.com/security/cve/CVE-2026-120059
  • web
    https://www.suse.com/security/cve/CVE-2026-120060
  • web
    https://www.suse.com/security/cve/CVE-2026-120061
  • web
    https://www.suse.com/security/cve/CVE-2026-120062
  • web
    https://www.suse.com/security/cve/CVE-2026-120063
  • web
    https://www.suse.com/security/cve/CVE-2026-120064
  • web
    https://www.suse.com/security/cve/CVE-2026-120065
  • web
    https://www.suse.com/security/cve/CVE-2026-120066
  • web
    https://www.suse.com/security/cve/CVE-2026-120067