Release date:
2026-11-06 15:44:36 UTC
Description:
* SECURITY UPDATE: psql meta-commands injected through plain-text dumps.
pg_dump, pg_dumpall and pg_restore copy object definitions and table
data from the source server into their plain-text scripts verbatim,
so a malicious or compromised source server could place psql
meta-commands such as \! in the dump, and psql ran them on the
machine restoring the dump, as the user running psql.
- debian/patches/CVE-2025-8714.patch: add a "restricted mode" to psql
(\restrict KEY refuses every meta-command until \unrestrict KEY with
the same key) and make pg_dump, pg_dumpall and pg_restore wrap every
plain-text script they write, by pg_restore both to --file and to
standard output, in \restrict/\unrestrict with a random key, settable
with the new --restrict-key option. Where the script switches
databases inside the restricted section (pg_dump and pg_restore
--create, and pg_dumpall moving the postgres or template1 database to
another tablespace), the \connect line is preceded by \unrestrict and
followed by \restrict, so psql runs the \connect itself unrestricted
and a restore with ON_ERROR_STOP does not stop at it; pg_dumpall
writes the \connect for each database it dumps between the restricted
sections (upstream c204bd39f7, ae63671a7f, e8bc40d290). PostgreSQL
9.5 has no pg_strong_random(), so the key is read from /dev/urandom
and the dump fails if that is not possible.
- debian/patches/CVE-2026-18408.patch: read the \unrestrict argument
up to the end of the line without backquote or variable expansion;
otherwise a dump could still run shell commands through
"\unrestrict `command`" while restricted (upstream 2006fca401).
- BEHAVIOUR CHANGE: every plain-text dump now starts with
"\restrict " and ends with "\unrestrict ", so two dumps of
the same database are no longer byte-identical unless the same
--restrict-key is given, and a psql without this update prints
"invalid command \restrict" when restoring such a dump (with
ON_ERROR_STOP it stops there, before restoring anything; otherwise
the restore continues unprotected). Scripts that insert their own
meta-commands into a dump must place them outside the
\restrict/\unrestrict section or use a known --restrict-key.
Custom, directory and tar archives are unchanged.
- CVE-2025-8714
- CVE-2026-18408
Updated packages:
-
libecpg-compat3_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:7a9a941748d7e8b43004e0659598cff794165380
-
libecpg-dev_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:eea3076b7fce237aae053f5b72b574a8ac831f42
-
libecpg6_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:640eabd4572da8e9aee81bcab53e812b5e53b119
-
libpgtypes3_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:9fc3cc725c515ba4732926ad1fcbb5618e58c737
-
libpq-dev_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:1fc18de02bf0b9ddcde556ecccf436f84d337b07
-
libpq5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:d034a85edfc6708ab4eda71009f09be0efc0c701
-
postgresql-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:b1fb1334a34d276d5aaba8baccd303093f9971b5
-
postgresql-client-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:634d855b95562f74d85baa769cf18eb90908d7e1
-
postgresql-contrib-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:8110893711eb87fad1212555759093a8b047852b
-
postgresql-doc-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_all.deb
sha:1a318b1035887651ca3fa4aca1d1dea0fb103b6f
-
postgresql-plperl-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:11e32fe87155248f0d6ffea0cd32053997793ab0
-
postgresql-plpython-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:e0aaace8add9cd9ccf2758e26024154df5c9250b
-
postgresql-plpython3-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:a2736bc669ad6f2bbcbe430f0417d3823554a30a
-
postgresql-pltcl-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:055481f163d011c4c9bef34149a5c829e09d8187
-
postgresql-server-dev-9.5_9.5.25-0ubuntu0.16.04.1+tuxcare.els22_amd64.deb
sha:91b7cc4830fe87faf094f4da265dbfa0899237c3
Notes:
This page is generated automatically and has not been checked for errors. For clarification or
corrections please contact the
CloudLinux Packaging Team.