CVE-2026-116314 · Runtime
NO FIX YET · SEE WHAT TO DO
A crafted archive passed to pg_restore can execute arbitrary operating system code as the user running pg_restore. An attacker who supplies the archive gets code execution on the machine running the restore.
first public Nov 12, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run pg_restore on archives from sources they do not fully trust, such as backups or dumps received from outside the organisation, are exposed. Systems that only restore archives they created themselves, or that never run pg_restore on untrusted input, are less exposed.
Not affected if managed-hosting, trusted-archives-only
Who cares database-admin, postgresql, self-hosted
psql -c "SHOW server_version;" or pg_restore --version to find the installed version18.7, 17.12, 16.16, 15.20 or 14.2518.7, 17.12, , or (the fixed release for each major line)Improper input validation in PostgreSQL pg_restore allows a non-plain archive provider to execute arbitrary code as the operating system user running pg_restore, 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 pg_restore OS process. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
16.1615.2014.25