The remote openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:22261-1 advisory.

    Changes in psqlODBC:

    - Update to 18.00.0006:
      * Large-object read overflows the application buffer         (CVE-2026-120057, bsc#1289252).
      * Row cache overflow when a later FETCH changes the column count         (CVE-2026-120058, bsc#1289253).
      * Driver uses a server-supplied column name as a format string         (CVE-2026-120059, bsc#1289254).
      * Driver does not validate server-supplied counts and lengths         (CVE-2026-120060, bsc#1289255).
      * ODBC escape parser stack buffer overflow         (CVE-2026-120061, bsc#1289256).
      * SQL injection through SQLSpecialColumns table and schema names         (CVE-2026-120062, bsc#1289257).
      * Stack buffer overflow when quoting long schema and table names         (CVE-2026-120063, bsc#1289258).
      * Driver does not validate column numbers and row indexes in         binding and descriptor functions         (CVE-2026-120064, bsc#1289259).
      * Driver does not escape a server-supplied column name in its         updatable-cursor queries (CVE-2026-120065, bsc#1289260).
      * Log files are created with default permissions at a predictable         path and follow symbolic links         (CVE-2026-120066, bsc#1289261).
      * Stack buffer overflow when reading the keyset (ctid/oid)         columns of an updatable cursor         (CVE-2026-120067, bsc#1289262).
      * 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.

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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 of its positioned SELECT, UPDATE, and DELETE     statements, without doubling any double quote in the name. A column name that contains a double quote     therefore changes the SQL that the driver runs with the application's privileges, including which rows a     positioned UPDATE or DELETE affects. Any database user who can create a table that the application reads     with an updatable cursor can choose such a name, and so can a server not trusted under current SSL     settings. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120065)

Note that Nessus relies on the presence of the package as reported by the vendor.

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:5191-1 advisory.

    - 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

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-3427 advisory.

    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 parameter number 32768 wraps that count to -32768. Binding     parameter 32769 then writes about 2.5 MB of zeros starting 1.25 MB before the binding array, which crashes     the application or leaves it running on a corrupted heap. Applications that build parameter lists from     untrusted input, such as an IN (?, ?, ...) list, are exposed. Versions before psqlODBC 18.00.0005 are     affected. (CVE-2026-109448)

    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 bytes than the buffer holds and overwrite adjacent     memory in the client process with server-chosen bytes. Fetching any large-object column is sufficient to     trigger it. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120057)

    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 columns and make the driver write tuple records past the end     of the heap allocation. A keyset reply with fewer columns than the key fields also underflows the unsigned     field count. This is reachable with UseDeclareFetch enabled. Versions before psqlODBC 18.00.0006 are     affected. (CVE-2026-120058)

    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.
    (CVE-2026-120059)

    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 fixed storage. Bytea octal decoding reads up to two     bytes past the end of a truncated escape sequence. A server not trusted under current SSL settings can     crash the client or make it read out of bounds. Versions before psqlODBC 18.00.0006 are affected.
    (CVE-2026-120060)

    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 a reference to an unsupplied argument copies arbitrary     bytes into the query. The copy of a {d}, {t}, {ts}, or {escape} body also writes one byte past a 128-byte     stack buffer. An application that forwards untrusted SQL text to the driver exposes its process to memory     corruption. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120061)

    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 describe its columns, and the target of the last     INSERT when the driver rewrites SELECT @@IDENTITY. In the @@IDENTITY rewrite, a column name sent by the     server can also write one byte past the buffer. The bytes written past the buffer are a double quote and a     NUL. An application that forwards untrusted SQL text to the driver exposes its process to stack     corruption. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120063)

    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_COUNT on an application row descriptor unbinds columns     at negative indexes. SQLColAttribute with a very large column number uses a negative index.
    SQLSetPos(SQL_ADD) does not check the row number against the rowset size. An application that forwards     untrusted column or row numbers exposes its process to out-of-bounds reads and writes. Versions before     psqlODBC 18.00.0006 are affected. (CVE-2026-120064)

    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 of its positioned SELECT, UPDATE, and DELETE     statements, without doubling any double quote in the name. A column name that contains a double quote     therefore changes the SQL that the driver runs with the application's privileges, including which rows a     positioned UPDATE or DELETE affects. Any database user who can create a table that the application reads     with an updatable cursor can choose such a name, and so can a server not trusted under current SSL     settings. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120065)

    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 local user can read query text and data from another     user's logs, and can place a symbolic link at the predictable path so that the driver appends log data to     a file of the attacker's choosing with the victim's privileges. Versions before psqlODBC 18.00.0006 are     affected. (CVE-2026-120066)

    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, so a value of 32 bytes or more writes past the buffer.
    A server not trusted under current SSL settings can send such a value. So can any database user who can     create a view with its own column named ctid that the application reads with an updatable cursor. Builds     with _FORTIFY_SOURCE abort; other builds overwrite adjacent stack memory. Versions before psqlODBC     18.00.0006 are affected. (CVE-2026-120067)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of postgresql-odbc installed on the remote host is prior to 09.03.0100-2. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2026-4103 advisory.

    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 bytes than the buffer holds and overwrite adjacent     memory in the client process with server-chosen bytes. Fetching any large-object column is sufficient to     trigger it. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120057)

    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.
    (CVE-2026-120059)

    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 of its positioned SELECT, UPDATE, and DELETE     statements, without doubling any double quote in the name. A column name that contains a double quote     therefore changes the SQL that the driver runs with the application's privileges, including which rows a     positioned UPDATE or DELETE affects. Any database user who can create a table that the application reads     with an updatable cursor can choose such a name, and so can a server not trusted under current SSL     settings. Versions before psqlODBC 18.00.0006 are affected. (CVE-2026-120065)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	名稱	產品	系列	已發布	已更新	嚴重性
379421	openSUSE 16 Security Update : psqlODBC (openSUSE-SU-2026:22261-1)	Nessus	SuSE Local Security Checks	2026/11/12	2026/11/12	high
375337	Linux Distros Unpatched Vulnerability : CVE-2026-120065	Nessus	Misc.	2026/11/2	2026/11/5	high
379484	SUSE SLED15 / SLES15 Security Update : psqlODBC (SUSE-SU-2026:5191-1)	Nessus	SuSE Local Security Checks	2026/11/12	2026/11/12	high
379879	Amazon Linux 2023 : postgresql-odbc, postgresql-odbc-tests (ALAS2023-2026-3427)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high
379819	Amazon Linux 2 : postgresql-odbc (ALAS-2026-4103)	Nessus	Amazon Linux Local Security Checks	2026/11/12	2026/11/12	high

偵測

搜尋 Plugin

high

high

high

high

high