CVE-2026-116314: PostgreSQL pg_restore executes arbitrary code due to missing non-plain archive validation

Published Nov 12, 2026
·
Updated

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

6 affected components
debian/postgresql-15*
debian/postgresql-17*
debian/postgresql-18*
debian/postgresql-15<=15.18-0+deb12u1, <=15.19-0+deb12u1
debian/postgresql-17<=17.11-0+deb13u1
debian/postgresql-18<=18.6-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 18.7
  2. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 17.12
  3. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 16.16
  4. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 15.20
  5. Upgrade

    Upgrade PostgreSQL to a version that resolves this vulnerability.

    Fixed in 14.25

Event History

Nov 12, 2026
CVE Published
via MITRE·02:15 PM
Data Sourced
via MITRE·02:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·06:47 PM
DescriptionAffected Software

Frequently Asked Questions

1

Which deployments are affected?

PostgreSQL installations using pg_restore are affected if they run a version before 18.7, 17.12, 16.16, 15.20, or 14.25 and restore a crafted non-plain archive.

2

What does an attacker need to exploit this issue?

An attacker needs to cause pg_restore to process a crafted non-plain archive. No PostgreSQL privileges are required by the vulnerability vector, but exploitation requires user interaction because someone must run pg_restore on the archive.

3

What level of access can successful exploitation provide?

Successful exploitation can execute arbitrary code as the operating system user that runs pg_restore. This is distinct from arbitrary SQL contained in archive data executing at the restore destination.

4

What should be prioritized if immediate patching is not possible?

Do not run pg_restore against untrusted non-plain archive files until an updated PostgreSQL version can be deployed. Treat archives from untrusted sources as potentially capable of executing code in the pg_restore process.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203