ALPINE-CVE-2026-116314: Input Validation
Improper input validation in PostgreSQL pgrestore allows a non-plain archive provider to execute arbitrary code as the operating system user running pgrestore, via a crafted archive. Note a contrast: crafted archive data may legitimately cause arbitrary SQL to execute at the restore destination, but it does not legitimately confer arbitrary code execution in the pgrestore OS process. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
alpine/postgresql15to a version that resolves this vulnerability.Fixed in 15.20-r0 - Upgrade
Upgrade
alpine/postgresql16to a version that resolves this vulnerability.Fixed in 16.16-r0 - Upgrade
Upgrade
alpine/postgresql17to a version that resolves this vulnerability.Fixed in 17.12-r0 - Upgrade
Upgrade
alpine/postgresql18to a version that resolves this vulnerability.Fixed in 18.7-r0 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 18.7 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 17.12 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 16.16 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 15.20 - Upgrade
Upgrade
PostgreSQLto a version that resolves this vulnerability.Fixed in 14.25
Event History
Frequently Asked Questions
Who is exposed to this vulnerability?
Systems that run pg_restore on a crafted non-plain PostgreSQL archive are exposed if they use PostgreSQL 14 before 14.25, 15 before 15.20, 16 before 16.16, 17 before 17.12, or 18 before 18.7. The listed Alpine packages are alpine/postgresql15, alpine/postgresql16, alpine/postgresql17, and alpine/postgresql18.
What does an attacker need to exploit it?
An attacker needs to cause pg_restore to process a crafted non-plain archive. Exploitation requires user interaction because someone must run pg_restore against the malicious archive, but the attacker does not need privileges on the target system.
What is the impact of successful exploitation?
A crafted archive can execute arbitrary code as the operating system user running pg_restore, with confidentiality, integrity, and availability impact at that user's privilege level. This is distinct from arbitrary SQL executed at the restore destination, which archive contents may legitimately cause.
How can this risk be reduced before updates are available?
Do not run pg_restore on untrusted or insufficiently verified non-plain archives. Treat archives from external or untrusted sources as potentially able to execute code in the pg_restore process and restore only with an operating system account whose permissions are appropriately limited.