{"id":"CVE-2026-6469","aliases":["ALPINE-CVE-2026-6469","AZL-95714","BELL-CVE-2026-6469","BIT-postgresql-2026-6469","DEBIAN-CVE-2026-6469","EUVD-2026-57855","GHSA-5qv4-w274-5rpv","MGASA-2026-0347","OESA-2026-3420","OESA-2026-3421","OESA-2026-3422","OESA-2026-3423","OESA-2026-3424","SUSE-SU-2026:23577-1","SUSE-SU-2026:23578-1","SUSE-SU-2026:23579-1","SUSE-SU-2026:23580-1","SUSE-SU-2026:23582-1","SUSE-SU-2026:3793-1","SUSE-SU-2026:3794-1","SUSE-SU-2026:3940-1","SUSE-SU-2026:3941-1","SUSE-SU-2026:3942-1","SUSE-SU-2026:3943-1","SUSE-SU-2026:3944-1","SUSE-SU-2026:3963-1","SUSE-SU-2026:4013-1","SUSE-SU-2026:4014-1","SUSE-SU-2026:4015-1","SUSE-SU-2026:4016-1","SUSE-SU-2026:4017-1","SUSE-SU-2026:4018-1","UBUNTU-CVE-2026-6469","USN-8653-1","openSUSE-SU-2026:11552-1","openSUSE-SU-2026:11553-1","openSUSE-SU-2026:11554-1","openSUSE-SU-2026:11555-1","openSUSE-SU-2026:11565-1","openSUSE-SU-2026:21699-1","openSUSE-SU-2026:21700-1","openSUSE-SU-2026:21701-1","openSUSE-SU-2026:21702-1","openSUSE-SU-2026:21703-1"],"status":"published","title":"PostgreSQL ALTER TABLE ALTER TYPE resets extended statistics ownership","description":"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.","severity":{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00318,"percentile":0.24926,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-708"],"published":"2026-08-13T13:00:16Z","modified":"2026-11-03T06:30:18Z","fixes":[{"ecosystem":"Alpine:v3.21","package":"postgresql15","fixed_in":["15.19-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"postgresql15","fixed_in":["15.19-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"postgresql16","fixed_in":["16.15-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"postgresql16","fixed_in":["16.15-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"postgresql16","fixed_in":["16.15-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"postgresql16","fixed_in":["16.15-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"postgresql17","fixed_in":["17.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"postgresql17","fixed_in":["17.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"postgresql17","fixed_in":["17.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"postgresql17","fixed_in":["17.11-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"postgresql18","fixed_in":["18.5-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"postgresql18","fixed_in":["18.5-r0"],"sources":["osv"]},{"ecosystem":"Azure Linux:3","package":"postgresql","fixed_in":["16.15-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"postgresql17","fixed_in":["17.11-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"postgresql18","fixed_in":["18.6-r0"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"postgresql","fixed_in":["14.24.0","15.19.0","16.15.0","17.11.0","18.5.0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"postgresql-15","fixed_in":["15.19-0+deb12u1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"postgresql-17","fixed_in":["17.11-0+deb13u1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"postgresql-18","fixed_in":["18.6-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"postgresql-14","fixed_in":["14.24-0ubuntu0.22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"postgresql-16","fixed_in":["16.15-0ubuntu0.24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:26.04:LTS","package":"postgresql-18","fixed_in":["18.6-0ubuntu0.26.04.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.21","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.5-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.5-r0"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"17.5-r0"},{"fixed":"17.11-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"18.0-r0"},{"fixed":"18.6-r0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"postgresql","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"14.24.0"},{"introduced":"15.0.0"},{"fixed":"15.19.0"},{"introduced":"16.0.0"},{"fixed":"16.15.0"},{"introduced":"17.0.0"},{"fixed":"17.11.0"},{"introduced":"18.0.0"},{"fixed":"18.5.0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"postgresql-15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-0+deb12u1"}]}],"versions":["15.10-0+deb12u1","15.11-0+deb12u1","15.12-0+deb12u1","15.12-0+deb12u2","15.13-0+deb12u1","15.14-0+deb12u1","15.15-0+deb12u1","15.16-0+deb12u1","15.17-0+deb12u1","15.18-0+deb12u1","15.3-0+deb12u1","15.3-1","15.4-0+deb12u1","15.4-1","15.4-2","15.4-3","15.5-0+deb12u1","15.6-0+deb12u1","15.7-0+deb12u1","15.8-0+deb12u1","15.9-0+deb12u1"]},{"source":"osv","ecosystem":"Debian:13","package":"postgresql-17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-0+deb13u1"}]}],"versions":["17.10-0+deb13u1","17.5-1","17.6-0+deb13u1","17.6-1","17.7-0+deb13u1","17.8-0+deb13u1","17.9-0+deb13u1"]},{"source":"osv","ecosystem":"Debian:14","package":"postgresql-18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-1"}]}],"versions":["18.0-1","18.1-1","18.1-2","18.2-1","18.3-1","18.4-1","18~beta1+20250612-1","18~beta1+20250624-1","18~beta1+20250701-1","18~beta1-1","18~beta2-1","18~beta3-1","18~rc1-1","18~rc1-2","18~rc1-3","18~~devel.20250318+g4078da6c478-1","18~~devel.20250331-1","18~~devel.20250405-1","18~~devel.20250421-1","18~~devel.20250502-1"]},{"source":"osv","ecosystem":"Mageia:10","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-1.mga10"}]}],"bundled":28},{"source":"osv","ecosystem":"Mageia:10","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-1.mga10"}]}],"bundled":28},{"source":"osv","ecosystem":"Mageia:9","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-1.mga9"}]}],"bundled":28},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-1.oe2403sp4"}]}],"bundled":24},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-1.oe2403sp1"}]}],"bundled":24},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"postgresql","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-1.oe2403sp3"}]}],"bundled":24},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP4","package":"postgresql-17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-1.oe2403sp4"}]}],"bundled":25},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"postgresql-17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-1.oe2403sp3"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-160000.1.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-160000.1.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-160000.1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-160000.1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-160000.1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-160000.1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-160000.1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-160000.1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-160000.1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-160000.1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-3.75.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-3.75.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-3.47.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-3.47.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-3.61.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-3.61.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150200.5.77.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150200.5.77.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150200.5.77.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150200.5.77.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150200.5.77.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150200.5.77.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-8.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-8.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150200.5.49.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150600.16.38.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150600.16.38.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150600.16.38.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150600.16.38.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-150600.16.38.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150200.5.33.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150600.13.16.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150600.13.16.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150600.13.16.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150600.13.16.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150600.13.16.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-150200.5.17.1"}]}],"bundled":28},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150600.13.32.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Package Hub 15 SP7","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150600.13.32.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP7","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150600.13.32.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150600.13.32.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-150600.13.32.1"}]}],"bundled":25},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP6-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP6","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150600.16.36.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP4-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 15 SP5-LTSS","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP4","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 15 SP5","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-150200.5.62.1"}]}],"bundled":24},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"postgresql-9.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["9.3.1-1","9.3.2-1","9.3.2-1ubuntu1","9.3.2-1ubuntu2","9.3.3-1","9.3.3-1bzr1","9.3.3-1bzr2","9.3.4-1","9.3.5-0ubuntu0.14.04.1","9.3.6-0ubuntu0.14.04","9.3.7-0ubuntu0.14.04","9.3.8-0ubuntu0.4.04","9.3.9-0ubuntu0.14.04","9.3.10-0ubuntu0.14.04","9.3.11-0ubuntu0.14.04","9.3.12-0ubuntu0.14.04","9.3.13-0ubuntu0.14.04","9.3.14-0ubuntu0.14.04","9.3.15-0ubuntu0.14.04","9.3.16-0ubuntu0.14.04","9.3.17-0ubuntu0.14.04","9.3.18-0ubuntu0.14.04.1","9.3.19-0ubuntu0.14.04","9.3.20-0ubuntu0.14.04","9.3.21-0ubuntu0.14.04","9.3.22-0ubuntu0.14.04","9.3.23-0ubuntu0.14.04","9.3.24-0ubuntu0.14.04","9.3.24-0ubuntu0.14.04+esm1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"postgresql-9.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["9.5.0-1","9.5.0-2","9.5.0-3","9.5.1-1","9.5.2-1","9.5.3-0ubuntu0.16.04","9.5.4-0ubuntu0.16.04","9.5.5-0ubuntu0.16.04","9.5.6-0ubuntu0.16.04","9.5.7-0ubuntu0.16.04","9.5.8-0ubuntu0.16.04.1","9.5.9-0ubuntu0.16.04","9.5.10-0ubuntu0.16.04","9.5.11-0ubuntu0.16.04","9.5.12-0ubuntu0.16.04","9.5.13-0ubuntu0.16.04","9.5.14-0ubuntu0.16.04","9.5.16-0ubuntu0.16.04.1","9.5.17-0ubuntu0.16.04.1","9.5.18-0ubuntu0.16.04.1","9.5.19-0ubuntu0.16.04.1","9.5.21-0ubuntu0.16.04.1","9.5.23-0ubuntu0.16.04.1","9.5.24-0ubuntu0.16.04.1","9.5.25-0ubuntu0.16.04.1","9.5.25-0ubuntu0.16.04.1+esm1","9.5.25-0ubuntu0.16.04.1+esm2","9.5.25-0ubuntu0.16.04.1+esm3","9.5.25-0ubuntu0.16.04.1+esm4","9.5.25-0ubuntu0.16.04.1+esm5","9.5.25-0ubuntu0.16.04.1+esm6","9.5.25-0ubuntu0.16.04.1+esm7","9.5.25-0ubuntu0.16.04.1+esm8","9.5.25-0ubuntu0.16.04.1+esm10"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"postgresql-10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["10.1-1","10.1-2","10.2-1","10.3-1","10.4-0ubuntu0.18.04","10.5-0ubuntu0.18.04","10.6-0ubuntu0.18.04.1","10.7-0ubuntu0.18.04.1","10.8-0ubuntu0.18.04.1","10.9-0ubuntu0.18.04.1","10.10-0ubuntu0.18.04.1","10.12-0ubuntu0.18.04.1","10.14-0ubuntu0.18.04.1","10.15-0ubuntu0.18.04.1","10.16-0ubuntu0.18.04.1","10.17-0ubuntu0.18.04.1","10.18-0ubuntu0.18.04.1","10.19-0ubuntu0.18.04.1","10.20-0ubuntu0.18.04.1","10.21-0ubuntu0.18.04.1","10.22-0ubuntu0.18.04.1","10.23-0ubuntu0.18.04.1","10.23-0ubuntu0.18.04.2","10.23-0ubuntu0.18.04.2+esm1","10.23-0ubuntu0.18.04.2+esm2","10.23-0ubuntu0.18.04.2+esm3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"postgresql-12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["12.0-1","12.1-1","12.1-2build1","12.2-1","12.2-1ubuntu2","12.2-4","12.4-0ubuntu0.20.04.1","12.5-0ubuntu0.20.04.1","12.6-0ubuntu0.20.04.1","12.7-0ubuntu0.20.04.1","12.8-0ubuntu0.20.04.1","12.9-0ubuntu0.20.04.1","12.10-0ubuntu0.20.04.1","12.11-0ubuntu0.20.04.1","12.12-0ubuntu0.20.04.1","12.13-0ubuntu0.20.04.1","12.14-0ubuntu0.20.04.1","12.15-0ubuntu0.20.04.1","12.16-0ubuntu0.20.04.1","12.17-0ubuntu0.20.04.1","12.18-0ubuntu0.20.04.1","12.19-0ubuntu0.20.04.1","12.20-0ubuntu0.20.04.1","12.22-0ubuntu0.20.04.1","12.22-0ubuntu0.20.04.2","12.22-0ubuntu0.20.04.4"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"postgresql-14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-0ubuntu0.22.04.1"}]}],"versions":["14.1-1ubuntu1","14.2-1","14.2-1ubuntu1","14.3-0ubuntu0.22.04.1","14.4-0ubuntu0.22.04.1","14.5-0ubuntu0.22.04.1","14.6-0ubuntu0.22.04.1","14.7-0ubuntu0.22.04.1","14.8-0ubuntu0.22.04.1","14.9-0ubuntu0.22.04.1","14.10-0ubuntu0.22.04.1","14.11-0ubuntu0.22.04.1","14.12-0ubuntu0.22.04.1","14.13-0ubuntu0.22.04.1","14.15-0ubuntu0.22.04.1","14.17-0ubuntu0.22.04.1","14.18-0ubuntu0.22.04.1","14.19-0ubuntu0.22.04.1","14.20-0ubuntu0.22.04.1","14.22-0ubuntu0.22.04.1","14.23-0ubuntu0.22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"postgresql-16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-0ubuntu0.24.04.1"}]}],"versions":["16.0-2","16.1-1","16.1-1build1","16.1-1build3","16.2-1","16.2-1ubuntu2","16.2-1ubuntu3","16.2-1ubuntu4","16.3-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.2","16.6-0ubuntu0.24.04.1","16.8-0ubuntu0.24.04.1","16.9-0ubuntu0.24.04.1","16.10-0ubuntu0.24.04.1","16.11-0ubuntu0.24.04.1","16.13-0ubuntu0.24.04.1","16.14-0ubuntu0.24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"postgresql-18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-0ubuntu0.26.04.1"}]}],"versions":["18.0-1","18.1-1","18.1-1ubuntu1","18.1-1ubuntu2","18.1-2","18.3-1","18.4-0ubuntu0.26.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"postgresql-14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-0ubuntu0.22.04.1"}]}],"versions":["14.1-1ubuntu1","14.2-1","14.2-1ubuntu1","14.3-0ubuntu0.22.04.1","14.4-0ubuntu0.22.04.1","14.5-0ubuntu0.22.04.1","14.6-0ubuntu0.22.04.1","14.7-0ubuntu0.22.04.1","14.8-0ubuntu0.22.04.1","14.9-0ubuntu0.22.04.1","14.10-0ubuntu0.22.04.1","14.11-0ubuntu0.22.04.1","14.12-0ubuntu0.22.04.1","14.13-0ubuntu0.22.04.1","14.15-0ubuntu0.22.04.1","14.17-0ubuntu0.22.04.1","14.18-0ubuntu0.22.04.1","14.19-0ubuntu0.22.04.1","14.20-0ubuntu0.22.04.1","14.22-0ubuntu0.22.04.1","14.23-0ubuntu0.22.04.1"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"postgresql-16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-0ubuntu0.24.04.1"}]}],"versions":["16.0-2","16.1-1","16.1-1build1","16.1-1build3","16.2-1","16.2-1ubuntu2","16.2-1ubuntu3","16.2-1ubuntu4","16.3-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.1","16.4-0ubuntu0.24.04.2","16.6-0ubuntu0.24.04.1","16.8-0ubuntu0.24.04.1","16.9-0ubuntu0.24.04.1","16.10-0ubuntu0.24.04.1","16.11-0ubuntu0.24.04.1","16.13-0ubuntu0.24.04.1","16.14-0ubuntu0.24.04.1"],"bundled":30},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"postgresql-18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-0ubuntu0.26.04.1"}]}],"versions":["18.0-1","18.1-1","18.1-1ubuntu1","18.1-1ubuntu2","18.1-2","18.3-1","18.4-0ubuntu0.26.04.1"],"bundled":30},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-1.1"}]}],"bundled":28},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"postgresql14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.24-160000.1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"postgresql15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"15.19-160000.1.1"}]}],"bundled":24},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"postgresql16","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"16.15-160000.1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"postgresql17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"17.11-160000.1.1"}]}],"bundled":25},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"postgresql18","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-160000.1.1"}]}],"bundled":28},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"postgresql18-mini","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"18.6-160000.1.1"}]}],"bundled":28}],"products":[{"vendor":"postgresql","product":"postgresql"}],"references":[{"url":"https://www.postgresql.org/support/security/CVE-2026-6469/","tags":["Vendor Advisory","advisory","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6469","tags":["web","advisory"]},{"url":"https://www.postgresql.org/support/security/CVE-2026-6469"},{"url":"https://github.com/advisories/GHSA-5qv4-w274-5rpv"},{"url":"https://security.alpinelinux.org/vuln/CVE-2026-6469","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-6469","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-6469","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0347.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36165","tags":["report"]},{"url":"https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/","tags":["web","report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3420","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14662","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14663","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14664","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14668","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14670","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14671","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14679","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14680","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-15741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-15742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-16239","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-16241","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18024","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-19385","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6464","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-6471","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3421","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3422","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14672","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-14681","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-3424","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623577-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1275001","tags":["report"]},{"url":"https://bugzilla.suse.com/1275002","tags":["report"]},{"url":"https://bugzilla.suse.com/1275042","tags":["report"]},{"url":"https://bugzilla.suse.com/1275043","tags":["report"]},{"url":"https://bugzilla.suse.com/1275044","tags":["report"]},{"url":"https://bugzilla.suse.com/1275046","tags":["report"]},{"url":"https://bugzilla.suse.com/1275047","tags":["report"]},{"url":"https://bugzilla.suse.com/1275048","tags":["report"]},{"url":"https://bugzilla.suse.com/1275049","tags":["report"]},{"url":"https://bugzilla.suse.com/1275050","tags":["report"]},{"url":"https://bugzilla.suse.com/1275051","tags":["report"]},{"url":"https://bugzilla.suse.com/1275052","tags":["report"]},{"url":"https://bugzilla.suse.com/1275053","tags":["report"]},{"url":"https://bugzilla.suse.com/1275054","tags":["report"]},{"url":"https://bugzilla.suse.com/1275055","tags":["report"]},{"url":"https://bugzilla.suse.com/1275056","tags":["report"]},{"url":"https://bugzilla.suse.com/1275057","tags":["report"]},{"url":"https://bugzilla.suse.com/1275058","tags":["report"]},{"url":"https://bugzilla.suse.com/1275059","tags":["report"]},{"url":"https://bugzilla.suse.com/1275060","tags":["report"]},{"url":"https://bugzilla.suse.com/1275061","tags":["report"]},{"url":"https://bugzilla.suse.com/1275062","tags":["report"]},{"url":"https://bugzilla.suse.com/1275063","tags":["report"]},{"url":"https://bugzilla.suse.com/1275064","tags":["report"]},{"url":"https://bugzilla.suse.com/1275065","tags":["report"]},{"url":"https://bugzilla.suse.com/1275066","tags":["report"]},{"url":"https://bugzilla.suse.com/1275067","tags":["report"]},{"url":"https://bugzilla.suse.com/1275068","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-14681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-15741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-15742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-16238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-16239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-16241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-18024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-18408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-19385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-6471","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623578-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623579-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623580-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623582-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263793-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263794-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263940-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263941-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263942-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263943-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263944-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20263963-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264013-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264014-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264015-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264016-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264017-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20264018-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-6469","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-6469","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8653-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-8714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-6464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-6470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-6471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-6473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14672","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-14681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-15741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-15742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-16238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-16239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-16241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-18024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-18408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-19385","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-6469","title":"PostgreSQL ALTER TABLE ALTER TYPE resets extended statistics ownership","description":"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.","status":"published","published":"2026-08-13T13:00:16.796Z","modified":"2026-08-29T23:07:35.319Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low","assessor":"cna"}],"cwes":["CWE-708"],"updated_at":"2026-11-02T13:49:53.818886Z"}],"euvd":[{"id":"EUVD-2026-57855","description":"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.","status":"published","published":"2026-08-13T13:00:16Z","modified":"2026-08-29T23:07:35Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low"}],"updated_at":"2026-11-02T18:01:21.466916Z"}],"ghsa":[{"id":"GHSA-5qv4-w274-5rpv","title":"Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership...","description":"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.","status":"published","published":"2026-08-13T15:34:37Z","modified":"2026-08-13T15:34:37Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low"}],"cwes":["CWE-708"],"updated_at":"2026-11-02T15:10:25.227735Z"}],"nvd":[{"id":"CVE-2026-6469","description":"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.","status":"published","published":"2026-08-13T13:19:16.47Z","modified":"2026-08-29T23:17:22.153Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low","assessor":"secondary"}],"cwes":["CWE-708"],"updated_at":"2026-11-02T14:12:37.217486Z"}],"osv":[{"id":"ALPINE-CVE-2026-6469","description":"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.","status":"published","published":"2026-08-13T13:19:16.47Z","modified":"2026-11-03T06:30:18.31280675Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low"}],"updated_at":"2026-11-03T06:41:39.834803Z"},{"id":"BELL-CVE-2026-6469","status":"published","published":"2026-08-18T06:06:07.694492Z","modified":"2026-08-22T07:15:05.277863775Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low"}],"updated_at":"2026-11-02T15:28:25.231222Z"},{"id":"DEBIAN-CVE-2026-6469","description":"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.","status":"published","published":"2026-08-13T13:19:16.47Z","modified":"2026-10-01T03:03:48.155767328Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low"}],"updated_at":"2026-11-02T15:45:58.699079Z"},{"id":"OESA-2026-3420","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026amp;apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):\n\nInteger 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\u0026apos;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)\n\nCleartext 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)\n\nHeap 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)\n\nIncomplete 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\u0026apos;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)\n\nType 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)\n\nHeap 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)\n\nHeap 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)\n\nType confusion in PostgreSQL module \u0026quot;refint\u0026quot; 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 \u0026quot;refint: Remove plan cache.\u0026quot;, without a CVE number.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-14671)\n\nUntrusted 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)\n\nInteger wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies.  This may execute arbitrary code as the operating system user running the database.  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-14677)\n\nBuffer 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)\n\nStack 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)\n\nType confusion with PostgreSQL \u0026quot;internal\u0026quot; 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 \u0026quot;internal\u0026quot; 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)\n\nSQL 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)\n\nInteger 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)\n\nType confusion in PostgreSQL \u0026quot;portal\u0026quot;/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)\n\nInteger underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix.  The client overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a simple SIGSEGV, 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)\n\nBuffer 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)\n\nUntrusted 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\u0026apos;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)\n\nHeap 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)\n\nUntrusted 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 \u0026quot;COPY FROM STDIN\u0026quot; or \u0026quot;\\copy FROM STDIN\u0026quot; command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands.  \u0026quot;COPY FROM\u0026quot; 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\u0026apos;t control.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-6464)\n\nIncorrect 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)\n\nMissing 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)\n\nMissing 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)","status":"published","published":"2026-08-20T09:55:35Z","modified":"2026-08-20T10:15:07.726113427Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:47.217107Z"},{"id":"OESA-2026-3421","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026amp;apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):\n\nInteger 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\u0026apos;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)\n\nCleartext 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)\n\nHeap 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)\n\nIncomplete 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\u0026apos;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)\n\nType 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)\n\nHeap 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)\n\nHeap 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)\n\nType confusion in PostgreSQL module \u0026quot;refint\u0026quot; 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 \u0026quot;refint: Remove plan cache.\u0026quot;, without a CVE number.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-14671)\n\nUntrusted 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)\n\nInteger wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies.  This may execute arbitrary code as the operating system user running the database.  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-14677)\n\nBuffer 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)\n\nStack 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)\n\nType confusion with PostgreSQL \u0026quot;internal\u0026quot; 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 \u0026quot;internal\u0026quot; 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)\n\nSQL 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)\n\nInteger 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)\n\nType confusion in PostgreSQL \u0026quot;portal\u0026quot;/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)\n\nInteger underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix.  The client overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a simple SIGSEGV, 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)\n\nBuffer 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)\n\nUntrusted 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\u0026apos;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)\n\nHeap 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)\n\nUntrusted 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 \u0026quot;COPY FROM STDIN\u0026quot; or \u0026quot;\\copy FROM STDIN\u0026quot; command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands.  \u0026quot;COPY FROM\u0026quot; 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\u0026apos;t control.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-6464)\n\nIncorrect 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)\n\nMissing 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)\n\nMissing 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)","status":"published","published":"2026-08-20T09:56:01Z","modified":"2026-08-20T10:15:07.725989771Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:47.217107Z"},{"id":"OESA-2026-3422","title":"postgresql security update","description":"PostgreSQL is an advanced Object-Relational database management system (DBMS). The base postgresql package contains the client programs that you\u0026amp;apos;ll need to access a PostgreSQL DBMS server, as well as HTML documentation for the whole system.  These client programs can be located on the same machine as the PostgreSQL server, or on a remote machine that accesses a PostgreSQL server over a network connection.  The PostgreSQL server can be found in the postgresql-server sub-package.\r\n\r\nSecurity Fix(es):\n\nInteger 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\u0026apos;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)\n\nCleartext 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)\n\nHeap 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)\n\nIncomplete 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\u0026apos;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)\n\nType 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)\n\nHeap 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)\n\nHeap 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)\n\nType confusion in PostgreSQL module \u0026quot;refint\u0026quot; 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 \u0026quot;refint: Remove plan cache.\u0026quot;, without a CVE number.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-14671)\n\nUntrusted 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)\n\nInteger wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies.  This may execute arbitrary code as the operating system user running the database.  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-14677)\n\nBuffer 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)\n\nStack 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)\n\nType confusion with PostgreSQL \u0026quot;internal\u0026quot; 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 \u0026quot;internal\u0026quot; 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)\n\nSQL 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)\n\nInteger 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)\n\nType confusion in PostgreSQL \u0026quot;portal\u0026quot;/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)\n\nInteger underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix.  The client overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a simple SIGSEGV, 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)\n\nBuffer 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)\n\nUntrusted 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\u0026apos;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)\n\nHeap 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)\n\nUntrusted 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 \u0026quot;COPY FROM STDIN\u0026quot; or \u0026quot;\\copy FROM STDIN\u0026quot; command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands.  \u0026quot;COPY FROM\u0026quot; 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\u0026apos;t control.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-6464)\n\nIncorrect 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)\n\nMissing 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)\n\nMissing 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)","status":"published","published":"2026-08-20T09:56:22Z","modified":"2026-08-20T10:15:07.717032375Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:47.217107Z"},{"id":"OESA-2026-3423","title":"postgresql-17 security update","description":"PostgreSQL client programs\r\n\r\nSecurity Fix(es):\n\nInteger 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\u0026apos;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)\n\nCleartext 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)\n\nHeap 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)\n\nIncomplete 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\u0026apos;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)\n\nType 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)\n\nHeap 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)\n\nHeap 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)\n\nType confusion in PostgreSQL module \u0026quot;refint\u0026quot; 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 \u0026quot;refint: Remove plan cache.\u0026quot;, without a CVE number.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-14671)\n\nObservable 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)\n\nInteger wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies.  This may execute arbitrary code as the operating system user running the database.  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-14677)\n\nBuffer 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)\n\nStack 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)\n\nType confusion with PostgreSQL \u0026quot;internal\u0026quot; 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 \u0026quot;internal\u0026quot; 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)\n\nImproper 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)\n\nSQL 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)\n\nInteger 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)\n\nType confusion in PostgreSQL \u0026quot;portal\u0026quot;/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)\n\nInteger underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix.  The client overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a simple SIGSEGV, 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)\n\nBuffer 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)\n\nUntrusted 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\u0026apos;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)\n\nHeap 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)\n\nUntrusted 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 \u0026quot;COPY FROM STDIN\u0026quot; or \u0026quot;\\copy FROM STDIN\u0026quot; command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands.  \u0026quot;COPY FROM\u0026quot; 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\u0026apos;t control.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-6464)\n\nIncorrect 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)\n\nMissing 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)\n\nMissing 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)","status":"published","published":"2026-08-20T09:56:50Z","modified":"2026-08-20T10:15:07.766957498Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:47.217107Z"},{"id":"OESA-2026-3424","title":"postgresql-17 security update","description":"PostgreSQL client programs\r\n\r\nSecurity Fix(es):\n\nInteger 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\u0026apos;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)\n\nCleartext 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)\n\nHeap 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)\n\nIncomplete 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\u0026apos;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)\n\nType 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)\n\nHeap 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)\n\nHeap 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)\n\nType confusion in PostgreSQL module \u0026quot;refint\u0026quot; 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 \u0026quot;refint: Remove plan cache.\u0026quot;, without a CVE number.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-14671)\n\nObservable 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)\n\nInteger wraparound in PostgreSQL 32-bit builds of pltcl and plperl allows an object creator to cause the server to undersize an allocation and write out-of-bounds via crafted function bodies.  This may execute arbitrary code as the operating system user running the database.  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-14677)\n\nBuffer 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)\n\nStack 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)\n\nType confusion with PostgreSQL \u0026quot;internal\u0026quot; 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 \u0026quot;internal\u0026quot; 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)\n\nImproper 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)\n\nSQL 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)\n\nInteger 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)\n\nType confusion in PostgreSQL \u0026quot;portal\u0026quot;/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)\n\nInteger underflow in PostgreSQL ECPG allows a database server administrator to achieve temporary denial of service against the ECPG client via sending a bytea value lacking the mandatory prefix.  The client overwrites a huge memory region with bytes outside attacker knowledge or control.  This typically yields a simple SIGSEGV, 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)\n\nBuffer 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)\n\nUntrusted 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\u0026apos;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)\n\nHeap 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)\n\nUntrusted 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 \u0026quot;COPY FROM STDIN\u0026quot; or \u0026quot;\\copy FROM STDIN\u0026quot; command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands.  \u0026quot;COPY FROM\u0026quot; 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\u0026apos;t control.  Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.(CVE-2026-6464)\n\nIncorrect 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)\n\nMissing 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)\n\nMissing 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)","status":"published","published":"2026-08-20T09:57:14Z","modified":"2026-08-20T10:15:08.938709116Z","cvss":[{"version":"3.1","score":8.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:47.217107Z"},{"id":"UBUNTU-CVE-2026-6469","description":"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.","status":"published","published":"2026-08-13T13:19:00Z","modified":"2026-09-02T19:35:58.133281496Z","cvss":[{"version":"3.1","score":3.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L","level":"low"}],"updated_at":"2026-11-02T16:56:53.710209Z"},{"id":"AZL-95714","title":"CVE-2026-6469 affecting package postgresql for versions less than 16.15-1","description":"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.","status":"published","published":"2026-08-13T13:19:16Z","modified":"2026-09-10T14:17:03.965432943Z","updated_at":"2026-11-02T15:28:12.028669Z"},{"id":"BIT-postgresql-2026-6469","title":"PostgreSQL ALTER TABLE ALTER TYPE resets extended statistics ownership","description":"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.","status":"published","published":"2026-08-19T08:53:03.349Z","modified":"2026-09-08T08:48:18.573561525Z","updated_at":"2026-11-02T15:28:34.724063Z"},{"id":"MGASA-2026-0347","title":"Updated postgresql18 \u0026 postgresql15 packages fix security vulnerabilities","description":"psql COPY FROM STDIN early failure processes data lines as psql\ncommands. (CVE-2026-6464)\nALTER TABLE ALTER TYPE resets extended statistics ownership.\n(CVE-2026-6469)\nFails to check type USAGE privilege. (CVE-2026-6470)\nLogical decoding can dlopen arbitrary file. (CVE-2026-6471)\ntsvector and tsquery undersize allocations, via integer wraparound.\n(CVE-2026-14662)\npgcrypto, for OpenSSL-disabled ciphers, silently encrypts to and\ndecrypts from cleartext. (CVE-2026-14663)\nRegexp heap buffer overflow executes arbitrary code. (CVE-2026-14664)\nRow security caching disregards role modifications. (CVE-2026-14666)\nctid type confusion in selectivity estimator discloses derivative of\narbitrary read. (CVE-2026-14668)\nto_char heap buffer overflow executes arbitrary code. (CVE-2026-14669)\nplperl tied object heap buffer overflow executes arbitrary code.\n(CVE-2026-14670)\nrefint plan cache type confusion executes arbitrary code.\n(CVE-2026-14671)\nObservable response discrepancy with non-default scram_iterations\nprovides user existence oracle. (CVE-2026-14672)\namcheck does not clear untrusted search path. (CVE-2026-14673)\npg_stat_statements heap buffer overflow executes arbitrary code.\n(CVE-2026-14676)\n32-bit pltcl and plperl undersize allocations, via integer wraparound.\n(CVE-2026-14677)\npg_trgm picksplit reads past end of buffer. (CVE-2026-14678)\nStack buffer overflow in argument match writes 0x0 and 0x1 to server\nmemory. (CVE-2026-14679)\nType confusion via \"internal\" arguments. (CVE-2026-14680)\nImproper enforcement of GSSAPI encryption when coupled with SSL.\n(CVE-2026-14681)\nExpression deparse allows SQL injection via EXTRACT argument.\n(CVE-2026-15741)\nfuzzystrmatch writes effectively-arbitrary addresses, via integer\nwraparound. (CVE-2026-15742)\nType confusion in pg_restore_attribute_stats() executes arbitrary code.\n(CVE-2026-16238)\nType confusion in cursor CLOSE + DECLARE executes arbitrary code.\n(CVE-2026-16239)\nECPG integer underflow can crash the client. (CVE-2026-16241)\nascii() function reads past end of buffer. (CVE-2026-18024)\npsql \\unrestrict lets superuser of pg_dump origin server execute\narbitrary code in psql client. (CVE-2026-18408)\npg_dump heap buffer overflow executes arbitrary code. (CVE-2026-19385)\n","status":"published","published":"2026-08-31T16:22:02Z","modified":"2026-08-31T16:41:22.87871239Z","updated_at":"2026-11-02T15:49:43.795591Z"},{"id":"openSUSE-SU-2026:11552-1","title":"postgresql14-14.24-1.1 on GA media","description":"These are all security issues fixed in the postgresql14-14.24-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-19T00:00:00Z","modified":"2026-08-21T09:15:33.600289762Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:11553-1","title":"postgresql15-15.19-1.1 on GA media","description":"These are all security issues fixed in the postgresql15-15.19-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-19T00:00:00Z","modified":"2026-08-21T09:15:15.71610713Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:11554-1","title":"postgresql16-16.15-1.1 on GA media","description":"These are all security issues fixed in the postgresql16-16.15-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-19T00:00:00Z","modified":"2026-08-21T09:15:15.716295262Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:11555-1","title":"postgresql17-17.11-1.1 on GA media","description":"These are all security issues fixed in the postgresql17-17.11-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-19T00:00:00Z","modified":"2026-08-21T09:15:31.913081665Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:11565-1","title":"libecpg6-18.6-1.1 on GA media","description":"These are all security issues fixed in the libecpg6-18.6-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-08-21T00:00:00Z","modified":"2026-08-22T18:23:35.172985758Z","updated_at":"2026-11-02T16:58:39.516824Z"},{"id":"openSUSE-SU-2026:21699-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql14:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 14.24:\n  * https://www.postgresql.org/docs/14/release-14-24.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:40:07Z","modified":"2026-08-31T18:15:05.095320149Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"openSUSE-SU-2026:21700-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql15:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 15.19:\n  * https://www.postgresql.org/docs/15/release-15-19.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:41:31Z","modified":"2026-08-31T18:15:05.263553577Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"openSUSE-SU-2026:21701-1","title":"Security update for postgresql16","description":"This update for postgresql16 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql16:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 16.15:\n  * https://www.postgresql.org/docs/16/release-16-15.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:41:31Z","modified":"2026-08-31T18:15:05.251104316Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"openSUSE-SU-2026:21702-1","title":"Security update for postgresql17","description":"This update for postgresql17 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql17:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 17.11:\n  * https://www.postgresql.org/docs/17/release-17-11.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:41:31Z","modified":"2026-08-31T18:15:05.247026199Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"openSUSE-SU-2026:21703-1","title":"Security update for postgresql18","description":"This update for postgresql18 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14676: `pg_stat_statements` heap buffer overflow executes arbitrary code (bsc#1275060).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16238: type confusion in `pg_restore_attribute_stats()` executes arbitrary code (bsc#1275052).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql18:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 18.6:\n  * https://www.postgresql.org/docs/18/release-18-6.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:29:24Z","modified":"2026-08-31T18:15:04.195139093Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:23577-1","title":"Security update for postgresql18","description":"This update for postgresql18 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14676: `pg_stat_statements` heap buffer overflow executes arbitrary code (bsc#1275060).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16238: type confusion in `pg_restore_attribute_stats()` executes arbitrary code (bsc#1275052).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql18:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 18.6:\n  * https://www.postgresql.org/docs/18/release-18-6.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:28:34Z","modified":"2026-09-29T18:23:09.391799802Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23578-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql14:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 14.24:\n  * https://www.postgresql.org/docs/14/release-14-24.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:39:23Z","modified":"2026-09-29T18:23:09.60143169Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23579-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql15:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 15.19:\n  * https://www.postgresql.org/docs/15/release-15-19.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:38:25Z","modified":"2026-09-29T18:23:10.283746368Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23580-1","title":"Security update for postgresql16","description":"This update for postgresql16 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql16:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 16.15:\n  * https://www.postgresql.org/docs/16/release-16-15.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:40:51Z","modified":"2026-09-29T18:23:18.099399757Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23582-1","title":"Security update for postgresql17","description":"This update for postgresql17 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via \"internal\" arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql17:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 17.11:\n  * https://www.postgresql.org/docs/17/release-17-11.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-30T15:40:51Z","modified":"2026-09-29T18:23:18.711769459Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:3793-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql14:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 14.24:\n  * https://www.postgresql.org/docs/14/release-14-24.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-25T12:32:11Z","modified":"2026-08-27T11:01:48.464149674Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3794-1","title":"Security update for postgresql16","description":"This update for postgresql16 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql16:\n\n- Let `llvmjit-devel` require the `llc` and `clang` binaries to fix build of extensions on SLE-16 and newer.\n- Use LLVM 15 on SLE-15 up to SP5 and LLVM 17 on SP6 and SP7.\n- Update to version 16.15:\n  * https://www.postgresql.org/docs/16/release-16-15.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-08-25T12:32:28Z","modified":"2026-08-27T11:01:47.755259075Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3940-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql15:\n\n- Update to version 15.19:\n  * https://www.postgresql.org/docs/15/release-15-19.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-03T07:32:35Z","modified":"2026-09-10T18:23:18.065659207Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3941-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql14:\n\n- Update to version 14.24:\n  * https://www.postgresql.org/docs/14/release-14-24.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-03T07:34:20Z","modified":"2026-09-10T18:23:18.15973487Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3942-1","title":"Security update for postgresql18","description":"This update for postgresql18 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14676: `pg_stat_statements` heap buffer overflow executes arbitrary code (bsc#1275060).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16238: type confusion in `pg_restore_attribute_stats()` executes arbitrary code (bsc#1275052).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql18:\n\n- Update to version 18.6:\n  * https://www.postgresql.org/docs/18/release-18-6.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-03T07:34:58Z","modified":"2026-09-10T18:23:21.572389423Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3943-1","title":"Security update for postgresql16","description":"This update for postgresql16 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql16:\n\n- Update to version 16.15:\n  * https://www.postgresql.org/docs/16/release-16-15.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-03T07:36:47Z","modified":"2026-09-10T18:23:21.577971663Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3944-1","title":"Security update for postgresql14","description":"This update for postgresql14 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql14:\n\n- Update to version 14.24:\n  * https://www.postgresql.org/docs/14/release-14-24.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-03T07:38:14Z","modified":"2026-09-10T18:23:46.066126726Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:3963-1","title":"Security update for postgresql16","description":"This update for postgresql16 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql16:\n\n- Update to version 16.15:\n  * https://www.postgresql.org/docs/16/release-16-15.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-03T13:34:01Z","modified":"2026-09-13T18:23:12.569730049Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:4013-1","title":"Security update for postgresql17","description":"This update for postgresql17 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql17:\n\n- Update to version 17.11:\n  * https://www.postgresql.org/docs/17/release-17-11.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-07T07:35:47Z","modified":"2026-09-13T18:23:15.162346526Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:4014-1","title":"Security update for postgresql18","description":"This update for postgresql18 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14676: `pg_stat_statements` heap buffer overflow executes arbitrary code (bsc#1275060).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16238: type confusion in `pg_restore_attribute_stats()` executes arbitrary code (bsc#1275052).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql18:\n\n- Update to version 18.6:\n  * https://www.postgresql.org/docs/18/release-18-6.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-07T07:36:31Z","modified":"2026-09-13T18:23:15.247483213Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:4015-1","title":"Security update for postgresql18","description":"This update for postgresql18 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14676: `pg_stat_statements` heap buffer overflow executes arbitrary code (bsc#1275060).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16238: type confusion in `pg_restore_attribute_stats()` executes arbitrary code (bsc#1275052).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql18:\n\n- Update to version 18.6:\n  * https://www.postgresql.org/docs/18/release-18-6.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-07T07:37:23Z","modified":"2026-09-13T18:23:15.459905089Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:4016-1","title":"Security update for postgresql17","description":"This update for postgresql17 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14672:  observable response discrepancy with non-default `scram_iterations` provides user existence\n  oracle (bsc#1275062).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-14681: improper enforcement of GSSAPI encryption when coupled with SSL (bsc#1275055).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql17:\n\n- Update to version 17.11:\n  * https://www.postgresql.org/docs/17/release-17-11.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-07T07:38:12Z","modified":"2026-09-13T18:23:15.457478757Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:4017-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql15:\n\n- Update to version 15.19:\n  * https://www.postgresql.org/docs/15/release-15-19.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-07T07:38:39Z","modified":"2026-09-13T18:23:15.456005763Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"SUSE-SU-2026:4018-1","title":"Security update for postgresql15","description":"This update for postgresql15 fixes the following issues:\n\n- CVE-2026-6464: `psql` `COPY FROM STDIN` early failure processes data lines as `psql` commands (bsc#1275046).\n- CVE-2026-6469: `ALTER TABLE ALTER TYPE` resets extended statistics ownership (bsc#1275044).\n- CVE-2026-6470: failure to check type `USAGE` privilege (bsc#1275043).\n- CVE-2026-6471: logical decoding can `dlopen` arbitrary file (bsc#1275042).\n- CVE-2026-14662: `tsvector` and `tsquery` undersize allocations, via integer wraparound (bsc#1275001).\n- CVE-2026-14663: `pgcrypto`, for OpenSSL-disabled ciphers, silently encrypts to and decrypts from cleartext\n  (bsc#1275002).\n- CVE-2026-14664: `regexp` heap buffer overflow executes arbitrary code (bsc#1275068).\n- CVE-2026-14666: row security caching disregards role modifications (bsc#1275067).\n- CVE-2026-14668: `ctid` type confusion in selectivity estimator discloses derivative of arbitrary read\n  (bsc#1275066).\n- CVE-2026-14669: `to_char` heap buffer overflow executes arbitrary code (bsc#1275065).\n- CVE-2026-14670: `plperl` tied object heap buffer overflow executes arbitrary code (bsc#1275064).\n- CVE-2026-14671: `refint` plan cache type confusion executes arbitrary code (bsc#1275063).\n- CVE-2026-14673: `amcheck` does not clear untrusted search path (bsc#1275061).\n- CVE-2026-14677: 32-bit `pltcl` and `plperl` undersize allocations, via integer wraparound (bsc#1275059).\n- CVE-2026-14678: `pg_trgm` `picksplit` reads past end of buffer (bsc#1275058).\n- CVE-2026-14679: stack buffer overflow in argument match writes `0x0` and `0x1` to server memory (bsc#1275057).\n- CVE-2026-14680: type confusion via 'internal' arguments (bsc#1275056).\n- CVE-2026-15741: expression deparse allows SQL injection via `EXTRACT` argument (bsc#1275054).\n- CVE-2026-15742: `fuzzystrmatch` writes effectively-arbitrary addresses, via integer wraparound (bsc#1275053).\n- CVE-2026-16239: type confusion in cursor `CLOSE + DECLARE` executes arbitrary code (bsc#1275051).\n- CVE-2026-16241: ECPG integer underflow can crash the client (bsc#1275050).\n- CVE-2026-18024: `ascii()` function reads past end of buffer (bsc#1275049).\n- CVE-2026-18408: `psql` `\\unrestrict` lets superuser of `pg_dump` origin server execute arbitrary code in `psql`\n  client (bsc#1275048).\n- CVE-2026-19385: `pg_dump` heap buffer overflow executes arbitrary code (bsc#1275047).\n\nChanges for postgresql15:\n\n- Update to version 15.19:\n  * https://www.postgresql.org/docs/15/release-15-19.html\n  * https://www.postgresql.org/about/news/postgresql-186-1711-1615-1519-1424-and-19-beta-3-released-3365/\n","status":"published","published":"2026-09-07T07:39:30Z","modified":"2026-09-13T18:23:15.456323369Z","updated_at":"2026-11-02T15:54:05.392906Z"},{"id":"USN-8653-1","title":"postgresql-14, postgresql-16, postgresql-18 vulnerabilities","description":"It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when\nan early failure occurred. An authenticated user could possibly use this\nissue to execute arbitrary SQL commands. (CVE-2026-6464)\n\nIt was discovered that PostgreSQL incorrectly reset extended statistics\nownership during ALTER TABLE ALTER TYPE operations. An attacker could\npossibly use this issue to obtain sensitive information or gain unintended\nprivileges. (CVE-2026-6469)\n\nIt was discovered that PostgreSQL failed to check the USAGE privilege on\ntypes. An authenticated user could possibly use this issue to obtain\nsensitive information. (CVE-2026-6470)\n\nIt was discovered that PostgreSQL logical decoding could load arbitrary\nshared libraries. An authenticated user could possibly use this issue to\nexecute arbitrary code. (CVE-2026-6471)\n\nIt was discovered that PostgreSQL had integer wraparound issues in tsvector\nand tsquery allocations. An authenticated user could possibly use this\nissue to execute arbitrary code. (CVE-2026-14662)\n\nIt was discovered that PostgreSQL pgcrypto silently used cleartext when\nOpenSSL-disabled ciphers were requested. An authenticated user could\npossibly use this issue to obtain sensitive information. (CVE-2026-14663)\n\nIt was discovered that PostgreSQL had a heap buffer overflow in regular\nexpression processing. An authenticated user could possibly use this issue\nto execute arbitrary code. (CVE-2026-14664)\n\nIt was discovered that PostgreSQL row security policies were not properly\ninvalidated when roles were modified. An attacker could possibly use this\nissue to bypass intended row security restrictions. (CVE-2026-14666)\n\nIt was discovered that PostgreSQL had a type confusion issue in the\nselectivity estimator involving ctid. An authenticated user could possibly\nuse this issue to obtain sensitive information. (CVE-2026-14668)\n\nIt was discovered that PostgreSQL had a heap buffer overflow in the to_char\nfunction. An authenticated user could possibly use this issue to execute\narbitrary code. (CVE-2026-14669)\n\nIt was discovered that PostgreSQL had a heap buffer overflow in the PL/Perl\ntied object handling. An authenticated user could possibly use this issue\nto execute arbitrary code. (CVE-2026-14670)\n\nIt was discovered that PostgreSQL had a type confusion issue in the\nreferential integrity plan cache. An authenticated user could possibly use\nthis issue to execute arbitrary code. (CVE-2026-14671)\n\nIt was discovered that PostgreSQL had an observable response discrepancy\nwhen non-default scram_iterations were used. A remote attacker could\npossibly use this issue to enumerate valid usernames. This issue only\naffected Ubuntu 24.04 LTS and Ubuntu 26.04 LTS. (CVE-2026-14672)\n\nIt was discovered that PostgreSQL amcheck did not clear untrusted search\npaths. An authenticated user could possibly use this issue to execute\narbitrary code. (CVE-2026-14673)\n\nIt was discovered that PostgreSQL had a heap buffer overflow in\npg_stat_statements. An authenticated user could possibly use this issue to\nexecute arbitrary code. This issue only affected Ubuntu 26.04 LTS.\n(CVE-2026-14676)\n\nIt was discovered that PostgreSQL had integer wraparound issues in PL/Tcl\nand PL/Perl allocations on 32-bit systems. An authenticated user could\npossibly use this issue to execute arbitrary code. (CVE-2026-14677)\n\nIt was discovered that PostgreSQL pg_trgm read past the end of a buffer\nduring picksplit operations. An authenticated user could possibly use this\nissue to obtain sensitive information. (CVE-2026-14678)\n\nIt was discovered that PostgreSQL had a stack buffer overflow in argument\nmatching. An authenticated user could possibly use this issue to corrupt\nserver memory. (CVE-2026-14679)\n\nIt was discovered that PostgreSQL had a type confusion issue when functions\nused internal arguments. An authenticated user could possibly use this\nissue to execute arbitrary code. (CVE-2026-14680)\n\nIt was discovered that PostgreSQL did not properly enforce GSSAPI\nencryption when used together with SSL. An attacker could possibly use this\nissue to perform a machine-in-the-middle attack and obtain sensitive\ninformation. This issue only affected Ubuntu 26.04 LTS. (CVE-2026-14681)\n\nIt was discovered that PostgreSQL allowed SQL injection through EXTRACT\narguments during expression deparsing. An authenticated user could possibly\nuse this issue to perform SQL injection attacks. (CVE-2026-15741)\n\nIt was discovered that PostgreSQL fuzzystrmatch had integer wraparound\nissues that could write to arbitrary addresses. An authenticated user could\npossibly use this issue to execute arbitrary code. (CVE-2026-15742)\n\nIt was discovered that PostgreSQL had a type confusion issue in\npg_restore_attribute_stats(). An authenticated user could possibly use this\nissue to execute arbitrary code. This issue only affected Ubuntu 26.04 LTS.\n(CVE-2026-16238)\n\nIt was discovered that PostgreSQL had a type confusion issue when handling\ncursor CLOSE and DECLARE operations. An authenticated user could possibly\nuse this issue to execute arbitrary code. (CVE-2026-16239)\n\nIt was discovered that PostgreSQL had an integer underflow in the ECPG\nclient library. An attacker could possibly use this issue to cause\nPostgreSQL to crash, resulting in a denial of service. (CVE-2026-16241)\n\nIt was discovered that PostgreSQL had an out-of-bounds read in the ascii()\nfunction. An authenticated user could possibly use this issue to obtain\nsensitive information. (CVE-2026-18024)\n\nIt was discovered that the psql \\unrestrict command allowed the superuser\nof a pg_dump origin server to execute arbitrary code in the psql client. An\nattacker could possibly use this issue to execute arbitrary code.\n(CVE-2026-18408)\n\nIt was discovered that PostgreSQL pg_dump had a heap buffer overflow. An\nattacker could possibly use this issue to execute arbitrary code.\n(CVE-2026-19385)","status":"published","published":"2026-08-20T11:42:58Z","modified":"2026-08-20T23:44:58.684078119Z","updated_at":"2026-11-02T16:58:25.103481Z"}]}}