Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more permissive than the GSS settings, the connection may continue with lesser protection. Within major versions 17-18, minor versions before PostgreSQL 18.6 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.

The version of PostgreSQL installed on the remote host is 17 prior to 17.11 or 18 prior to 18.6. As such, it is potentially affected by a security bypass vulnerability:

  - Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI     contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to     require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more     permissive than the GSS settings, the connection may continue with lesser protection. Within major versions     17-18, minor versions before PostgreSQL 18.6 and 17.11 are affected. Versions before PostgreSQL 17 are     unaffected. (CVE-2026-14681)

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

The remote openSUSE 16 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21703-1 advisory.

    - CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands     (bsc#1275046).
    - CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).
    - CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).
    - CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).
    - CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).
    - CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from     cleartext       (bsc#1275002).
    - CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).
    - CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).
    - CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read       (bsc#1275066).
    - CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).
    - CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).
    - CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).
    - CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user     existence       oracle (bsc#1275062).
    - CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).
    - CVE-2026-14676: `pg_stat_statements` heap buffer overflow executes arbitrary code (bsc#1275060).
    - CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).
    - CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).
    - CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory     (bsc#1275057).
    - CVE-2026-14680: type confusion via internal arguments (bsc#1275056).
    - CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).
    - CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).
    - CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound     (bsc#1275053).
    - CVE-2026-16238: type confusion in `pg_restore_attribute_stats()` executes arbitrary code (bsc#1275052).
    - CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).
    - CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).
    - CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).
    - CVE-2026-18408: `psql` `\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in     `psql`       client (bsc#1275048).
    - CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).

    Changes for postgresql18:

    - Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and     newer.
    - Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.
    - Update to version 18.6:
      * https://www.postgresql.org/docs/18/release-18-6.html
      * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/

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 remote openSUSE 16 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21702-1 advisory.

    - CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands     (bsc#1275046).
    - CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).
    - CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).
    - CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).
    - CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).
    - CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from     cleartext       (bsc#1275002).
    - CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).
    - CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).
    - CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read       (bsc#1275066).
    - CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).
    - CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).
    - CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).
    - CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user     existence       oracle (bsc#1275062).
    - CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).
    - CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).
    - CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory     (bsc#1275057).
    - CVE-2026-14680: type confusion via internal arguments (bsc#1275056).
    - CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).
    - CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).
    - CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound     (bsc#1275053).
    - CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).
    - CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).
    - CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).
    - CVE-2026-18408: `psql` `\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in     `psql`       client (bsc#1275048).
    - CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).

    Changes for postgresql17:

    - Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and     newer.
    - Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.
    - Update to version 17.11:
      * https://www.postgresql.org/docs/17/release-17-11.html
      * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/

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-2076 advisory.

    Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database     user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs.
    This may execute arbitrary code as the operating system user running the database.  These types are     typically sourced from application logic, not taken from the application's user.  Hence, application users     attacking the database, through the application as a conduit, are unlikely.  CVE-2026-6473 had fixed     similar problems.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
    (CVE-2026-14662)

    Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct     observation of the faulty ciphertext.  The OpenSSL version and OpenSSL configuration determine the     disabled ciphers.  If the application accepts encrypted data as input, decryption will succeed even with     the wrong key.  This in turn loses the modest protection from the Modification Detection Code (MDC).
    Affected functions are pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt,     pgp_sym_encrypt_bytea, pgp_sym_decrypt_bytea, pgp_pub_encrypt_bytea, and pgp_pub_decrypt_bytea.  Versions     before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14663)

    Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the     operating system user running the database, via text that would not pass encoding validation.  This shares     heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through     pg_wchar.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14664)

    Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership     allows a query to continue using cached row-level security policies after those changes require a     different policy, via plan reuse.  Stale policies continue until some other event invalidates the cache or     connection termination ends the session.  This permits a user to complete reads and modifications that     were recently permitted but now forbidden.  An attacker must tailor an attack to a particular     application's pattern of privilege removal and role-specific row security policies.  Versions before     PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14666)

    Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator     to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid     input.  While the calculation loses precision, substantial memory value recovery appears possible.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14668)

    Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute     arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14669)

    Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute     arbitrary code as the operating system user running the database, via a crafted function body.  Versions     before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14670)

    Type confusion in PostgreSQL module refint allows an object creator to execute arbitrary code as the     operating system user running the database.  The fix for this emerged as a non-security bug report, and     the fix appear in the git repository with subject refint: Remove plan cache., without a CVE number.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14671)

    Observable response discrepancy in PostgreSQL SCRAM authentication allows an unauthenticated user to test     the existence of a user via observing the SCRAM iteration count.  This requires the probed user to have a     non-default scram_iterations count, because the authentication challenge for a nonexistent user reports     the default scram_iterations.  Within major versions 16-18, minor versions before PostgreSQL 18.5, 17.11,     and 16.15 are affected.  Versions before PostgreSQL 16 are unaffected. (CVE-2026-14672)

    Buffer over-read in PostgreSQL pg_trgm index picksplit function reads past end of a heap buffer.  This     might allow a table maintainer to infer limited memory values, via the lossy signal of index split     choices.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14678)

    Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown     impacts via OUT parameter count.  The attack can write only 0x0 and 0x1 bytes.  Versions before PostgreSQL     18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14679)

    Type confusion with PostgreSQL internal data type arguments allows any user to execute arbitrary code as     the operating system user running the database, via calls to functions with that argument type.  Type     internal represents a class of mutually-incompatible data structures not intended for access from SQL.
    The system intended to prevent such function calls, but this prevention had gaps.  Versions before     PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14680)

    Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI     contrary to pg_hba.conf rules, via initial direct TLS connection.  Despite a pg_hba.conf that appears to     require GSSAPI, the connection may exchange data over TLS encryption alone.  If the TLS settings are more     permissive than the GSS settings, the connection may continue with lesser protection.  Within major     versions 17-18, minor versions before PostgreSQL 18.5 and 17.11 are affected.  Versions before PostgreSQL     17 are unaffected. (CVE-2026-14681)

    SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a     superuser via a hostile object definition.  Attacks affect expression deparse consumers broadly, including     pg_dump, psql commands like \sf, and any similar usage in non-core tools.  Versions before PostgreSQL     18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-15741)

    Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of     addresses, executing arbitrary code as the operating system user running the database, via extreme inputs     to SQL function levenshtein() or levenshtein_less_equal().  Versions before PostgreSQL 18.5, 17.11, 16.15,     15.19, and 14.24 are affected. (CVE-2026-15742)

    Type confusion in PostgreSQL portal/cursor lifecycle allows a user to execute arbitrary code as the     operating system user running the database, via re-creation of a cursor or other portal with different     types.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-16239)

    Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of     service against the ECPG client via sending a byte value lacking the mandatory prefix.  The client     overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a     simple SIGSEV, but rare cases might achieve client-specific integrity impact via the write.  Versions     before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-16241)

    Buffer over-read in PostgreSQL ascii() SQL function allows a user to disclose up to 3 bytes after the end     of a specific allocation, via a crafted text value.  This is the same class of defect that CVE-2026-2006     fixed, though this instance has less impact.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and     14.24 are affected. (CVE-2026-18024)

    Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to     inject arbitrary code for restore-time execution as the client operating system account running psql to     restore the dump, via psql \restrict meta-command input expansion.  The fix for CVE-2025-8714 introduced     \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack.
    pg_dumpall is also affected.  pg_restore is affected when used to generate a plain-format dump.  Non-core     use of \restrict would be affected, but we've not identified non-core use.  Versions before PostgreSQL     18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-18408)

    Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to     execute arbitrary code as the operating system user running pg_dump, via a crafted transform list.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-19385)

    Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of     data lines as psql commands, via error injection.  If the COPY FROM STDIN or \copy FROM STDIN command     fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql     commands.  COPY FROM with a filename is unaffected.  The server administrator has no inherent control     over the data rows, so a complete attack requires the attacker to separately acquire control of both the     server and the data rows.  Alternatively, an attacker controlling data rows alone might complete an attack     through a coincidental error that they don't control.  Versions before PostgreSQL 18.5, 17.11, 16.15,     15.19, and 14.24 are affected. (CVE-2026-6464)

    Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of     dependent statistics objects to the current user.  This wrongly allows the table owner to run DROP     STATISTICS and ALTER STATISTICS via this improper ownership.  It wrongly denies those commands to the     prior statistics object owner.  DROP TABLE remains able to remove statistics objects, so this exploit     achieves nothing in many ownership arrangements.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19,     and 14.24 are affected. (CVE-2026-6469)

    Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service     against ALTER and DROP of the type, via creating a dependency on the type.  Many DDL operations did check     the privilege, but assigning a range subtype and referencing the type from an SQL expression did not.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-6470)

    Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege     to dlopen any file visible to the operating system account running the server, via the choice of logical     decoding plugin.  This in turn runs arbitrary code as that account.  Versions before PostgreSQL 18.5,     17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-6471)

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.

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

    Integer wraparound in PostgreSQL tsvector and tsquery data type functions allows an unprivileged database     user to cause the server to undersize an allocation and write out-of-bounds, via crafted large inputs.
    This may execute arbitrary code as the operating system user running the database.  These types are     typically sourced from application logic, not taken from the application's user.  Hence, application users     attacking the database, through the application as a conduit, are unlikely.  CVE-2026-6473 had fixed     similar problems.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
    (CVE-2026-14662)

    Cleartext storage in PostgreSQL pgcrypto disabled ciphers allows a user to recover cleartext, via direct     observation of the faulty ciphertext.  The OpenSSL version and OpenSSL configuration determine the     disabled ciphers.  If the application accepts encrypted data as input, decryption will succeed even with     the wrong key.  This in turn loses the modest protection from the Modification Detection Code (MDC).
    Affected functions are pgp_sym_encrypt, pgp_sym_decrypt, pgp_pub_encrypt, pgp_pub_decrypt,     pgp_sym_encrypt_bytea, pgp_sym_decrypt_bytea, pgp_pub_encrypt_bytea, and pgp_pub_decrypt_bytea.  Versions     before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14663)

    Heap buffer overflow in PostgreSQL regexp allows the query author to execute arbitrary code as the     operating system user running the database, via text that would not pass encoding validation.  This shares     heritage with CVE-2026-2006, but this case involved unanticipated data growth when round-tripped through     pg_wchar.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14664)

    Incomplete tracking in PostgreSQL of changes to role membership, role attributes, and database ownership     allows a query to continue using cached row-level security policies after those changes require a     different policy, via plan reuse.  Stale policies continue until some other event invalidates the cache or     connection termination ends the session.  This permits a user to complete reads and modifications that     were recently permitted but now forbidden.  An attacker must tailor an attack to a particular     application's pattern of privilege removal and role-specific row security policies.  Versions before     PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14666)

    Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator     to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid     input.  While the calculation loses precision, substantial memory value recovery appears possible.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14668)

    Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute     arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14669)

    Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute     arbitrary code as the operating system user running the database, via a crafted function body.  Versions     before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14670)

    Type confusion in PostgreSQL module refint allows an object creator to execute arbitrary code as the     operating system user running the database.  The fix for this emerged as a non-security bug report, and     the fix appear in the git repository with subject refint: Remove plan cache., without a CVE number.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14671)

    Observable response discrepancy in PostgreSQL SCRAM authentication allows an unauthenticated user to test     the existence of a user via observing the SCRAM iteration count.  This requires the probed user to have a     non-default scram_iterations count, because the authentication challenge for a nonexistent user reports     the default scram_iterations.  Within major versions 16-18, minor versions before PostgreSQL 18.5, 17.11,     and 16.15 are affected.  Versions before PostgreSQL 16 are unaffected. (CVE-2026-14672)

    Untrusted search path in PostgreSQL amcheck allows a grantee of amcheck function EXECUTE privilege to     execute arbitrary functions as the owners of expression indexes that depend on the search path, via     setting a hostile search path before calling the amcheck function.  Within major versions 18, 16, 15, and     14, minor versions before PostgreSQL 18.5, 16.15, 15.19, and 14.24 are affected.  PostgreSQL 17 is     unaffected. (CVE-2026-14673)

    Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as     the operating system user running the database, via crafted queries containing array constants.  Within     major version 18, minor versions before PostgreSQL 18.5 are affected.  Versions before PostgreSQL 18 are     unaffected. (CVE-2026-14676)

    Buffer over-read in PostgreSQL pg_trgm index picksplit function reads past end of a heap buffer.  This     might allow a table maintainer to infer limited memory values, via the lossy signal of index split     choices.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14678)

    Stack buffer overflow in PostgreSQL argument name matching allows an object creator to achieve unknown     impacts via OUT parameter count.  The attack can write only 0x0 and 0x1 bytes.  Versions before PostgreSQL     18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14679)

    Type confusion with PostgreSQL internal data type arguments allows any user to execute arbitrary code as     the operating system user running the database, via calls to functions with that argument type.  Type     internal represents a class of mutually-incompatible data structures not intended for access from SQL.
    The system intended to prevent such function calls, but this prevention had gaps.  Versions before     PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-14680)

    Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI     contrary to pg_hba.conf rules, via initial direct TLS connection.  Despite a pg_hba.conf that appears to     require GSSAPI, the connection may exchange data over TLS encryption alone.  If the TLS settings are more     permissive than the GSS settings, the connection may continue with lesser protection.  Within major     versions 17-18, minor versions before PostgreSQL 18.5 and 17.11 are affected.  Versions before PostgreSQL     17 are unaffected. (CVE-2026-14681)

    SQL injection in PostgreSQL EXTRACT() deparse allows an object owner to execute arbitrary SQL as a     superuser via a hostile object definition.  Attacks affect expression deparse consumers broadly, including     pg_dump, psql commands like \sf, and any similar usage in non-core tools.  Versions before PostgreSQL     18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-15741)

    Integer wraparound in PostgreSQL fuzzystrmatch allows a user to direct writes to a huge range of     addresses, executing arbitrary code as the operating system user running the database, via extreme inputs     to SQL function levenshtein() or levenshtein_less_equal().  Versions before PostgreSQL 18.5, 17.11, 16.15,     15.19, and 14.24 are affected. (CVE-2026-15742)

    Type confusion in PostgreSQL pg_restore_attribute_stats() allows an object creator to execute arbitrary     code as the operating system user running the database, via conflation of range and multirange values.
    Within major version 18, minor versions before PostgreSQL 18.5 are affected.  Versions before PostgreSQL     18 are unaffected. (CVE-2026-16238)

    Type confusion in PostgreSQL portal/cursor lifecycle allows a user to execute arbitrary code as the     operating system user running the database, via re-creation of a cursor or other portal with different     types.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-16239)

    Integer underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of     service against the ECPG client via sending a byte value lacking the mandatory prefix.  The client     overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a     simple SIGSEV, but rare cases might achieve client-specific integrity impact via the write.  Versions     before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-16241)

    Buffer over-read in PostgreSQL ascii() SQL function allows a user to disclose up to 3 bytes after the end     of a specific allocation, via a crafted text value.  This is the same class of defect that CVE-2026-2006     fixed, though this instance has less impact.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and     14.24 are affected. (CVE-2026-18024)

    Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to     inject arbitrary code for restore-time execution as the client operating system account running psql to     restore the dump, via psql \restrict meta-command input expansion.  The fix for CVE-2025-8714 introduced     \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack.
    pg_dumpall is also affected.  pg_restore is affected when used to generate a plain-format dump.  Non-core     use of \restrict would be affected, but we've not identified non-core use.  Versions before PostgreSQL     18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-18408)

    Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to     execute arbitrary code as the operating system user running pg_dump, via a crafted transform list.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-19385)

    Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of     data lines as psql commands, via error injection.  If the COPY FROM STDIN or \copy FROM STDIN command     fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql     commands.  COPY FROM with a filename is unaffected.  The server administrator has no inherent control     over the data rows, so a complete attack requires the attacker to separately acquire control of both the     server and the data rows.  Alternatively, an attacker controlling data rows alone might complete an attack     through a coincidental error that they don't control.  Versions before PostgreSQL 18.5, 17.11, 16.15,     15.19, and 14.24 are affected. (CVE-2026-6464)

    Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of     dependent statistics objects to the current user.  This wrongly allows the table owner to run DROP     STATISTICS and ALTER STATISTICS via this improper ownership.  It wrongly denies those commands to the     prior statistics object owner.  DROP TABLE remains able to remove statistics objects, so this exploit     achieves nothing in many ownership arrangements.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19,     and 14.24 are affected. (CVE-2026-6469)

    Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service     against ALTER and DROP of the type, via creating a dependency on the type.  Many DDL operations did check     the privilege, but assigning a range subtype and referencing the type from an SQL expression did not.
    Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-6470)

    Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege     to dlopen any file visible to the operating system account running the server, via the choice of logical     decoding plugin.  This in turn runs arbitrary code as that account.  Versions before PostgreSQL 18.5,     17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-6471)

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 FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 05d311bc-9991-11f1-bc50-6cc21735f730 advisory.

    The PostgreSQL project reports:

              CVE-2026-6464: psql COPY FROM STDIN, if the copy fails               before data rows begin, processes the following data lines               as psql commands.


              CVE-2026-6469: ALTER TABLE ALTER TYPE incorrectly reassigns               ownership of dependent extended statistics objects to the               current user.


              CVE-2026-6470: Missing privilege check for type USAGE allows               denial of service against ALTER and DROP of the type.


              CVE-2026-6471: Logical decoding lets a REPLICATION-               privileged user dlopen an arbitrary file via the decoding               plugin choice, running arbitrary code as the server's OS               user.


              CVE-2026-14662: Integer wraparound in tsvector and tsquery               functions can undersize an allocation, causing a buffer               overflow and arbitrary code execution.


              CVE-2026-14663: pgcrypto silently encrypts to and decrypts               from cleartext for ciphers OpenSSL has disabled, letting an               attacker recover cleartext.


              CVE-2026-14664: Heap buffer overflow in the regexp engine               allows arbitrary code execution via crafted input text.


              CVE-2026-14666: Row-level security policy caching can retain               a stale policy after role changes, letting a user complete               now-forbidden reads or writes.


              CVE-2026-14668: Type confusion in the ctid selectivity               estimator discloses a derivative of an arbitrary 4-byte span               of server memory.


              CVE-2026-14669: Heap buffer overflow in to_char(timestamptz)               via a long POSIX timezone abbreviation allows arbitrary code               execution.


              CVE-2026-14670: Heap buffer overflow in plperl, on return of               a tied hash, allows the function owner to execute arbitrary               code.


              CVE-2026-14671: Type confusion in module refint allows an               object creator to execute arbitrary code.


              CVE-2026-14672: SCRAM authentication reveals whether a role               exists via an observable difference in the reported               iteration count.


              CVE-2026-14673: amcheck fails to clear an untrusted search               path, letting an EXECUTE grantee run arbitrary functions as               an expression index's owner.


              CVE-2026-14676: Heap buffer overflow in pg_stat_statements               via crafted queries with array constants allows arbitrary               code execution.


              CVE-2026-14677: Integer wraparound in 32-bit pltcl/plperl               builds can undersize an allocation, allowing arbitrary code               execution.


              CVE-2026-14678: pg_trgm's picksplit function reads past the               end of a heap buffer, potentially disclosing limited memory.


              CVE-2026-14679: Stack buffer overflow in argument-name               matching lets an object creator write a few attacker-               influenced bytes into server memory.


              CVE-2026-14680: Type confusion via internal-typed function               arguments allows any user to execute arbitrary code.


              CVE-2026-14681: GSSAPI encryption is not properly enforced               when coupled with an initial direct SSL connection.


              CVE-2026-15741: Expression deparse of EXTRACT() allows SQL               injection via a hostile object definition, affecting pg_dump               and psql.


              CVE-2026-15742: Integer wraparound in fuzzystrmatch's               levenshtein() functions allows writes to arbitrary addresses               and code execution.


              CVE-2026-16238: Type confusion in               pg_restore_attribute_stats() allows arbitrary code execution               via conflated range/multirange values.


              CVE-2026-16239: Type confusion via cursor DECLARE and CLOSE               allows a user to execute arbitrary code.


              CVE-2026-16241: Integer underflow in ECPG can crash the               client via a bytea value lacking its mandatory prefix.


              CVE-2026-18024: The ascii() function reads past the end of a               buffer, disclosing a few bytes of server memory.


              CVE-2026-18408: psql's \unrestrict lets a malicious pg_dump               origin-server superuser execute arbitrary code in the               restoring client.


              CVE-2026-19385: Heap buffer overflow in pg_dump, when               dumping long function transform lists, allows arbitrary code               execution.


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

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

There are packages installed that are affected by multiple vulnerabilities referenced in the following CVEs:

  - Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to
    inject arbitrary code for restore-time execution as the client operating system account running psql to
    restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced
    \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack.
    pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core
    use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL
    18.6, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-18408)

  - Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of
    data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command
    fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql
    commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over
    the data rows, so a complete attack requires the attacker to separately acquire control of both the server
    and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through
    a coincidental error that they don't control. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and
    14.24 are affected. (CVE-2026-6464)

  - Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of
    dependent statistics objects to the current user. This wrongly allows the table owner to run DROP
    STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the prior
    statistics object owner. DROP TABLE remains able to remove statistics objects, so this exploit achieves
    nothing in many ownership arrangements. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24
    are affected. (CVE-2026-6469)

  - Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service
    against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check
    the privilege, but assigning a range subtype and referencing the type from an SQL expression did not.
    Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected. (CVE-2026-6470)

  - Missing authorization in PostgreSQL logical decoding allows a non-superuser holding REPLICATION privilege
    to dlopen any file visible to the operating system account running the server, via the choice of logical
    decoding plugin. This in turn runs arbitrary code as that account. Versions before PostgreSQL 18.6, 17.11,
    16.15, 15.19, and 14.24 are affected. (CVE-2026-6471)

The remote Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6438 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6438-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     August 13, 2026                       https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : postgresql-17     CVE ID         : CVE-2026-6464 CVE-2026-6469 CVE-2026-6470 CVE-2026-6471                      CVE-2026-6473 CVE-2026-14662 CVE-2026-14663 CVE-2026-14664                      CVE-2026-14666 CVE-2026-14668 CVE-2026-14669 CVE-2026-14670                      CVE-2026-14671 CVE-2026-14672 CVE-2026-14673 CVE-2026-14677                      CVE-2026-14678 CVE-2026-14679 CVE-2026-14680 CVE-2026-14681                      CVE-2026-15741 CVE-2026-15742 CVE-2026-16239 CVE-2026-16241                      CVE-2026-18024 CVE-2026-18408 CVE-2026-19385

    Multiple security issues were discovered in PostgreSQL, which may     result in execution of arbitrary code, incorrect authentication,     information disclosure, or privilege escalation.

    The upstream fix to address CVE-2026-6471 requires additional changes     to the configuration if some extensions are used. This affects the     postgresql-17-wal2json, postgresql-17-squeeze, postgresql-17-pg-rewrite     and postgresql-17-decoderbufs extensions included in Debian.
    Quoting from the changelog:

    | Restrict logical decoding output plugins to the set specified by     | a new server parameter `output_plugin_libraries` (Jacob     | Champion)     | Previously, a replication user could select any loadable library     |     | Restrict logical decoding output plugins to the set specified by     | a new server parameter `output_plugin_libraries` (Jacob     | Champion)     | Previously, a replication user could select any loadable library     | for logical decoding, allowing exploits of various sorts. To     | allow locking this down without breaking setups that worked     | before, introduce a whitelist of allowed output plugins.
    |     | By default, only the output plugins shipped as part of     | PostgreSQL (`pgoutput` and `test_decoding`) are included in     |`output_plugin_libraries`. Installations that rely on other     | output plugins must add them after updating the server, for     | example     |     | output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'

    For the stable distribution (trixie), these problems have been fixed in     version 17.11-0+deb13u1.

    We recommend that you upgrade your postgresql-17 packages.

    For the detailed security status of postgresql-17 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/postgresql-17

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian 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.

  - Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI     contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to     require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more     permissive than the GSS settings, the connection may continue with lesser protection. Within major     versions 17-18, minor versions before PostgreSQL 18.6 and 17.11 are affected. Versions before PostgreSQL     17 are unaffected. (CVE-2026-14681)

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

ID	Name	Product	Family	Type	Severity
342121	PostgreSQL 17.x < 17.11 / 18.x < 18.6 GSSAPI Improper Message Integrity Enforcement	Nessus	Databases	Combined	medium
342116	openSUSE 16: libecpg6 / libpq5 / postgresql18 / postgresql18-contrib / etc (openSUSE-SU-2026:21703-1)	Nessus	SuSE Local Security Checks	Local	high
342107	openSUSE 16: postgresql17 / postgresql17-contrib / postgresql17-devel / etc (openSUSE-SU-2026:21702-1)	Nessus	SuSE Local Security Checks	Local	high
341882	Amazon Linux 2023 : postgresql17, postgresql17-contrib, postgresql17-llvmjit (ALAS2023-2026-2076)	Nessus	Amazon Linux Local Security Checks	Local	high
341834	Amazon Linux 2023 : postgresql18, postgresql18-contrib, postgresql18-llvmjit (ALAS2023-2026-2079)	Nessus	Amazon Linux Local Security Checks	Local	high
335950	FreeBSD : PostgreSQL -- Multiple vulnerabilities (05d311bc-9991-11f1-bc50-6cc21735f730)	Nessus	FreeBSD Local Security Checks	Local	high
445997	Alpine: postgresql15: security update to 15.19-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	high
445997	Alpine: postgresql15: security update to 15.19-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	high
445996	Alpine: multiple libecpg packages, multiple postgresql18 packages: security update to 18.5-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	high
445996	Alpine: multiple libecpg packages, multiple postgresql18 packages: security update to 18.5-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	high
445995	Alpine: multiple postgresql17 packages: security update to 17.11-r0	Tenable Cloud Security	Alpine Linux Local Security Checks	Local	high
445995	Alpine: multiple postgresql17 packages: security update to 17.11-r0	Tenable Self-Hosted Container Security	Alpine Linux Local Security Checks	Local	high
335238	Debian dsa-6438 : libecpg-compat3 - security update	Nessus	Debian Local Security Checks	Local	high
335210	Linux Distros Unpatched Vulnerability : CVE-2026-14681	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-14681

medium

Tenable Plugins

medium

high

high

high

high

high

high

high

high

high

high

high

high

medium