The remote SUSE Linux SLES12 / SLES_SAP12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3794-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-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-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 postgresql16:

    - 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 16.15:
      * https://www.postgresql.org/docs/16/release-16-15.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-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.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-2077 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)

    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)

    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)

    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.

The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ ciqsa-2026_1565 advisory.

    This advisory aggregates security fixes for the postgresql SRPM in CIQ LTS 9.6. It addresses 37 CVEs:
    CVE-2026-14673, CVE-2026-6477, CVE-2026-14664, CVE-2026-6473, CVE-2026-6472, and 32 more.

Tenable has extracted the preceding description block directly from the CIQ 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 Ubuntu 22.04 LTS / 24.04 LTS / 26.04 LTS host has packages installed that are affected by multiple vulnerabilities as referenced in the USN-8653-1 advisory.

    It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when an early failure occurred. An     authenticated user could possibly use this issue to execute arbitrary SQL commands. (CVE-2026-6464)

    It was discovered that PostgreSQL incorrectly reset extended statistics ownership during ALTER TABLE ALTER     TYPE operations. An attacker could possibly use this issue to obtain sensitive information or gain     unintended privileges. (CVE-2026-6469)

    It was discovered that PostgreSQL failed to check the USAGE privilege on types. An authenticated user     could possibly use this issue to obtain sensitive information. (CVE-2026-6470)

    It was discovered that PostgreSQL logical decoding could load arbitrary shared libraries. An authenticated     user could possibly use this issue to execute arbitrary code. (CVE-2026-6471)

    It was discovered that PostgreSQL had integer wraparound issues in tsvector and tsquery allocations. An     authenticated user could possibly use this issue to execute arbitrary code. (CVE-2026-14662)

    It was discovered that PostgreSQL pgcrypto silently used cleartext when OpenSSL-disabled ciphers were     requested. An authenticated user could possibly use this issue to obtain sensitive information.
    (CVE-2026-14663)

    It was discovered that PostgreSQL had a heap buffer overflow in regular expression processing. An     authenticated user could possibly use this issue to execute arbitrary code. (CVE-2026-14664)

    It was discovered that PostgreSQL row security policies were not properly invalidated when roles were     modified. An attacker could possibly use this issue to bypass intended row security restrictions.
    (CVE-2026-14666)

    It was discovered that PostgreSQL had a type confusion issue in the selectivity estimator involving ctid.
    An authenticated user could possibly use this issue to obtain sensitive information. (CVE-2026-14668)

    It was discovered that PostgreSQL had a heap buffer overflow in the to_char function. An authenticated     user could possibly use this issue to execute arbitrary code. (CVE-2026-14669)

    It was discovered that PostgreSQL had a heap buffer overflow in the PL/Perl tied object handling. An     authenticated user could possibly use this issue to execute arbitrary code. (CVE-2026-14670)

    It was discovered that PostgreSQL had a type confusion issue in the referential integrity plan cache. An     authenticated user could possibly use this issue to execute arbitrary code. (CVE-2026-14671)

    It was discovered that PostgreSQL had an observable response discrepancy when non-default scram_iterations     were used. A remote attacker could possibly use this issue to enumerate valid usernames. This issue only     affected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-14672)

    It was discovered that PostgreSQL amcheck did not clear untrusted search paths. An authenticated user     could possibly use this issue to execute arbitrary code. (CVE-2026-14673)

    It was discovered that PostgreSQL had a heap buffer overflow in pg_stat_statements. An authenticated user     could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS.
    (CVE-2026-14676)

    It was discovered that PostgreSQL had integer wraparound issues in PL/Tcl and PL/Perl allocations on     32-bit systems. An authenticated user could possibly use this issue to execute arbitrary code.
    (CVE-2026-14677)

    It was discovered that PostgreSQL pg_trgm read past the end of a buffer during picksplit operations. An     authenticated user could possibly use this issue to obtain sensitive information. (CVE-2026-14678)

    It was discovered that PostgreSQL had a stack buffer overflow in argument matching. An authenticated user     could possibly use this issue to corrupt server memory. (CVE-2026-14679)

    It was discovered that PostgreSQL had a type confusion issue when functions used internal arguments. An     authenticated user could possibly use this issue to execute arbitrary code. (CVE-2026-14680)

    It was discovered that PostgreSQL did not properly enforce GSSAPI encryption when used together with SSL.
    An attacker could possibly use this issue to perform a machine-in-the-middle attack and obtain sensitive     information. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-14681)

    It was discovered that PostgreSQL allowed SQL injection through EXTRACT arguments during expression     deparsing. An authenticated user could possibly use this issue to perform SQL injection attacks.
    (CVE-2026-15741)

    It was discovered that PostgreSQL fuzzystrmatch had integer wraparound issues that could write to     arbitrary addresses. An authenticated user could possibly use this issue to execute arbitrary code.
    (CVE-2026-15742)

    It was discovered that PostgreSQL had a type confusion issue in pg_restore_attribute_stats(). An     authenticated user could possibly use this issue to execute arbitrary code. This issue only affected     Ubuntu 26.04 LTS. (CVE-2026-16238)

    It was discovered that PostgreSQL had a type confusion issue when handling cursor CLOSE and DECLARE     operations. An authenticated user could possibly use this issue to execute arbitrary code.
    (CVE-2026-16239)

    It was discovered that PostgreSQL had an integer underflow in the ECPG client library. An attacker could     possibly use this issue to cause PostgreSQL to crash, resulting in a denial of service. (CVE-2026-16241)

    It was discovered that PostgreSQL had an out-of-bounds read in the ascii() function. An authenticated user     could possibly use this issue to obtain sensitive information. (CVE-2026-18024)

    It was discovered that the psql \unrestrict command allowed the superuser of a pg_dump origin server to     execute arbitrary code in the psql client. An attacker could possibly use this issue to execute arbitrary     code. (CVE-2026-18408)

    It was discovered that PostgreSQL pg_dump had a heap buffer overflow. An attacker could possibly use this     issue to execute arbitrary code. (CVE-2026-19385)

Tenable has extracted the preceding description block directly from the Ubuntu 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	名前	製品	ファミリー	公開日	更新日	深刻度
341035	SUSE SLES12: postgresql16 / postgresql16-contrib / postgresql16-devel / etc (SUSE-SU-2026:3794-1)	Nessus	SuSE Local Security Checks	2026/8/27	2026/8/29	high
341834	Amazon Linux 2023 : postgresql18, postgresql18-contrib, postgresql18-llvmjit (ALAS2023-2026-2079)	Nessus	Amazon Linux Local Security Checks	2026/8/31	2026/9/18	high
341847	Amazon Linux 2023 : postgresql15, postgresql15-contrib, postgresql15-llvmjit (ALAS2023-2026-2077)	Nessus	Amazon Linux Local Security Checks	2026/8/31	2026/8/31	high
354872	Rocky Linux 9.6 [CIQ] Security Update: postgresql / postgresql-contrib / postgresql-docs / etc Multiple Vulnerabilities (ciqsa-2026_1565)	Nessus	Rocky Linux Local Security Checks	2026/10/1	2026/10/12	high
365387	Ubuntu 22.04 LTS / 24.04 LTS / 26.04 LTS : PostgreSQL vulnerabilities (USN-8653-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	high

検出

プラグインの検索

high

high

high

high

high