CVE-2026-116330
PostgreSQL pg_dump tar restore.sql fails to block psql command injection
- High 8.8
Description
Untrusted data inclusion in PostgreSQL pg_dump tar-format restore.sql allows a compromised origin server to execute arbitrary code as the client operating system account running psql, via the predictable restriction key in restore.sql. This is a gap in the fix for CVE-2025-8714. restore.sql is undocumented. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Key facts
- Published
- 12 Nov 2026
- Last changed
- 14 Nov 2026
- Assigned by
- PostgreSQL
- EPSS
- 0.373% likely to be exploited in the next 30 days, higher than 31.752% of CVEs (scores for 15 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 8.8CVSS 3.1, Highfrom the CNA (PostgreSQL)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
What to do
- use pg_restore instead of running restore.sqlCNA workaround statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | PostgreSQL |
|
Timeline
- 12 Nov 2026 Published