VYPR

rpm package

almalinux/pgvector

pkg:rpm/almalinux/pgvector

Vulnerabilities (15)

  • CVE-2026-6478MedMay 14, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may

  • CVE-2026-6477HigMay 14, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lseek64(), and lo_tell64() functions allows the server superuser to overwrite a client stack buffer with an arbitrarily-large response. Like gets(), PQfn(..., resu

  • CVE-2026-6475HigMay 14, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implic

  • CVE-2026-6473HigMay 14, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to undersize an allocation and write out-of-bounds. This may execute arbitrary code as the operating system user running the database. In applications that pass gi

  • CVE-2026-2006HigFeb 12, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Missing validation of multibyte character length in PostgreSQL text manipulation allows a database user to issue crafted queries that achieve a buffer overrun. That suffices to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL

  • CVE-2026-2005HigFeb 12, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Heap buffer overflow in PostgreSQL pgcrypto allows a ciphertext provider to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

  • CVE-2026-2004HigFeb 12, 2026
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Missing validation of type of input in PostgreSQL intarray extension selectivity estimator function allows an object creator to execute arbitrary code as the operating system user running the database. Versions before PostgreSQL 18.2, 17.8, 16.12, 15.16, and 14.21 are affected.

  • CVE-2025-12818MedNov 13, 2025
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Integer wraparound in multiple PostgreSQL libpq client library functions allows an application input provider or network peer to cause libpq to undersize an allocation and write out-of-bounds by hundreds of megabytes. This results in a segmentation fault for the application usin

  • CVE-2025-12817LowNov 13, 2025
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Missing authorization in PostgreSQL CREATE STATISTICS command allows a table owner to achieve denial of service against other CREATE STATISTICS users by creating in any schema. A later CREATE STATISTICS for the same name, from a user having the CREATE privilege, would then fail.

  • CVE-2025-8715HigAug 14, 2025
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    Improper neutralization of newlines in pg_dump in PostgreSQL allows a user 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 meta-commands inside a purpose-crafted object name

  • CVE-2025-8714HigAug 14, 2025
    affected < 0.6.2-2.module_el9.6.0+167+4e561146fixed 0.6.2-2.module_el9.6.0+167+4e561146

    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 meta-commands. pg_dumpall is also affected.

  • CVE-2025-1094HigFeb 13, 2025
    affected < 0.6.2-1.module_el9.5.0+120+4533eb20fixed 0.6.2-1.module_el9.5.0+120+4533eb20

    Improper neutralization of quoting syntax in PostgreSQL libpq functions PQescapeLiteral(), PQescapeIdentifier(), PQescapeString(), and PQescapeStringConn() allows a database input provider to achieve SQL injection in certain usage patterns. Specifically, SQL injection requires t

  • CVE-2024-10979HigNov 14, 2024
    affected < 0.6.2-1.module_el9.5.0+120+4533eb20fixed 0.6.2-1.module_el9.5.0+120+4533eb20

    Incorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to change sensitive process environment variables (e.g. PATH). That often suffices to enable arbitrary code execution, even if the attacker lacks a database server operating sys

  • CVE-2024-10978MedNov 14, 2024
    affected < 0.6.2-1.module_el9.5.0+120+4533eb20fixed 0.6.2-1.module_el9.5.0+120+4533eb20

    Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change different rows from those intended. An attack requires the application to use SET ROLE, SET SESSION AUTHORIZATION, or an equivalent feature. The problem arises when an appli

  • CVE-2024-10976MedNov 14, 2024
    affected < 0.6.2-1.module_el9.5.0+120+4533eb20fixed 0.6.2-1.module_el9.5.0+120+4533eb20

    Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change different rows from those intended. CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row security and user ID changes. They missed cases where a subquery, WITH qu