PostgreSQL
PostgreSQL pg_restore executes arbitrary code due to missing non-plain archive validation
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.8high · scored by CNA · CWE-20
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
n/a PostgreSQL
- >= 18, < 18.7
- >= 17, < 17.12
- >= 16, < 16.16
- >= 15, < 15.20
- < 14.25
Fixed in 18.7, 17.12, 16.16, 15.20, 14.25
Mitigation
Upgrade PostgreSQL to 18.7 or 17.12 or 16.16 or 15.20 or 14.25 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.