Back Linuxsecurity

openSUSE postgresql18 Important Arbitrary Code Exec Vuln 2026-0881

Linuxsecurity •LinuxSecurity Advisories • March 12, 2026

This update for postgresql18 fixes the following issues: Update to version 18.3 (bsc#1258754). Security issues fixed: * CVE-2026-2003: improper validation of type "oidvector" may allow disclose a few bytes of server memory (bsc#1258008). * CVE-2026-2004: intarray missing validation of type of input to selectivity estimator could lead to arbitrary code execution (bsc#1258009). * CVE-2026-2005: buffer overrun in contrib/pgcrypto's PGP decryption functions could lead to arbitrary code execution (bsc#1258010). * CVE-2026-2006: inadequate validation of multibyte character lengths could lead to arbitrary code execution (bsc#1258011). * CVE-2026-2007: pg_trgm heap buffer overflow can cause to write pattern onto server memory (bsc#1258012). Regression fixes: * the substring() function raises an error "invalid byte sequence for encoding" on non-ASCII text values if the source of that value is a database column (caused by CVE-2026-2006 fix). * a standby

## Patch Instructions: To install this SUSE update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Alternatively you can run the command listed for your product: * openSUSE Leap 15.6 zypper in -t patch SUSE-2026-881=1 openSUSE-SLE-15.6-2026-881=1 * Basesystem Module 15-SP7 zypper in -t patch SUSE-SLE-Module-Basesystem-15-SP7-2026-881=1 * SUSE Package Hub 15 15-SP7 zypper in -t patch SUSE-SLE-Module-Packagehub-Subpackages-15-SP7-2026-881=1 * Server Applications Module 15-SP7 zypper in -t patch SUSE-SLE-Module-Server-Applications-15-SP7-2026-881=1 * SUSE Linux Enterprise Server 15 SP6 LTSS zypper in -t patch SUSE-SLE-Product-SLES-15-SP6-LTSS-2026-881=1 * SUSE Linux Enterprise Server for SAP Applications 15 SP6 zypper in -t patch SUSE-SLE-Product-SLES_SAP-15-SP6-2026-881=1

## Patch Instructions:

To install this SUSE update use the SUSE recommended installation methods like

YaST online_update or "zypper patch".

Alternatively you can run the command listed for your product:

zypper in -t patch SUSE-2026-881=1 openSUSE-SLE-15.6-2026-881=1

* Basesystem Module 15-SP7

zypper in -t patch SUSE-SLE-Module-Basesystem-15-SP7-2026-881=1

* SUSE Package Hub 15 15-SP7

zypper in -t patch SUSE-SLE-Module-Packagehub-Subpackages-15-SP7-2026-881=1

* Server Applications Module 15-SP7

zypper in -t patch SUSE-SLE-Module-Server-Applications-15-SP7-2026-881=1

* SUSE Linux Enterprise Server 15 SP6 LTSS

zypper in -t patch SUSE-SLE-Product-SLES-15-SP6-LTSS-2026-881=1

* SUSE Linux Enterprise Server for SAP Applications 15 SP6

zypper in -t patch SUSE-SLE-Product-SLES_SAP-15-SP6-2026-881=1

* openSUSE Leap 15.6 (aarch64 ppc64le s390x x86_64 i586) * postgresql18-server-18.3-150600.13.8.1 * postgresql18-plpython-18.3-150600.13.8.1 * postgresql18-plperl-18.3-150600.13.8.1 * postgresql18-server-debuginfo-18.3-150600.13.8.1 * postgresql18-devel-18.3-150600.13.8.1 * postgresql18-plpython-debuginfo-18.3-150600.13.8.1 * libecpg6-18.3-150600.13.8.1 * postgresql18-18.3-150600.13.8.1 * postgresql18-devel-mini-18.3-150600.13.8.1 * postgresql18-plperl-debuginfo-18.3-150600.13.8.1 * postgresql18-devel-debuginfo-18.3-150600.13.8.1 * postgresql18-devel-mini-debuginfo-18.3-150600.13.8.1 * libecpg6-debuginfo-18.3-150600.13.8.1 * postgresql18-debuginfo-18.3-150600.13.8.1 * postgresql18-llvmjit-debuginfo-18.3-150600.13.8.1 * postgresql18-llvmjit-devel-18.3-150600.13.8.1 * postgresql18-pltcl-debuginfo-18.3-150600.13.8.1 * postgresql18-server-devel-debuginfo-18.3-150600.13.8.1 * Read the Full Advisory

* openSUSE Leap 15.6 (aarch64 ppc64le s390x x86_64 i586)

* postgresql18-server-18.3-150600.13.8.1

* postgresql18-plpython-18.3-150600.13.8.1

* postgresql18-plperl-18.3-150600.13.8.1

* postgresql18-server-debuginfo-18.3-150600.13.8.1

* postgresql18-devel-18.3-150600.13.8.1

* postgresql18-plpython-debuginfo-18.3-150600.13.8.1

* libecpg6-18.3-150600.13.8.1

* postgresql18-18.3-150600.13.8.1

* postgresql18-devel-mini-18.3-150600.13.8.1

* postgresql18-plperl-debuginfo-18.3-150600.13.8.1

* postgresql18-devel-debuginfo-18.3-150600.13.8.1

* postgresql18-devel-mini-debuginfo-18.3-150600.13.8.1

* libecpg6-debuginfo-18.3-150600.13.8.1

* postgresql18-debuginfo-18.3-150600.13.8.1

* postgresql18-llvmjit-debuginfo-18.3-150600.13.8.1

* postgresql18-llvmjit-devel-18.3-150600.13.8.1

* postgresql18-pltcl-debuginfo-18.3-150600.13.8.1

* postgresql18-server-devel-debuginfo-18.3-150600.13.8.1

* bsc#1258008 * bsc#1258009 * bsc#1258010 * bsc#1258011 * bsc#1258012 * bsc#1258754 ## References: * * * * * * * * * * *

The full story

This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.

Critical Vulnerabilities in PostgreSQL 18 and 16 Require Immediate Attention On March 12, 2026, updates for PostgreSQL versions 16 and 18 were released, addressing multiple critical vulnerabilities. Key issues include CVE-2026-2003, CVE-2026-2004, CVE-2026-2005, CVE-2026-2006, and CVE-2026-2007, all published on February 12, 2026. These vulnerabilities could lead to arbitrary code execution and memory disclosure, affecting server security. Users of openSUSE and SUSE Linux Enterprise are particularly at risk and are advised to apply the patches immediately. The updates also include regression fixes for issues related to the substring() function and multibyte character handling. The vulnerabilities are significant, with CVE-2026-2004, CVE-2026-2005, and CVE-2026-2006 rated 8.8 on the CVSS scale, indicating high severity. The current status is that patches are available, and users are urged to update their systems promptly. 3 sources 72

Extracted Entities

Companies (2)

OpenSUSE SuSE

CVEs (5)

CVE-2026-2003 CVE-2026-2004 CVE-2026-2005 CVE-2026-2006 CVE-2026-2007