Security Digest · Vulnerability record
CVE-2026-116314: PostgreSQL pg_restore executes arbitrary code due to missing non-plain archive 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.
CVSS 8.8 High EPSS 0.5% · p43 Patch this week
Should you act?
Normal patch cycle
No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.5%, percentile 43: FIRST’s model estimates a 0.5% chance of exploitation activity in the next 30 days, higher than 43% of all scored CVEs (low). EPSS is a probability, not a verdict.
- Needs a user to click or open something. Phishing makes that realistic, but it is not wormable.
- Editorial verdict: Patch this week. PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE — An attacker needs a database login first, and no attacks have been reported, but crash code is public, 32 of the fixes are rated 8.8, and any role that can create objects can reach code execution, so update every server and client this week.
What it is
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.
Weakness type: CWE-20.
Product: PostgreSQL · Assigned by: PostgreSQL · Published: 2026-11-12
Affected and fixed versions
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| n/a | PostgreSQL | 18 < 18.7, 17 < 17.12, 16 < 16.16, 15 < 15.20, < 14.25 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| PostgreSQL | 3.1 | 8.8 High | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: required (a user must click/open something)
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-11-21): 0.49% probability of exploitation activity in the next 30 days; percentile 43.
Timeline
- — CVE record published by PostgreSQL
- — erroneo.us brief: PostgreSQL Fixes 52 CVEs, Including CVE-2026-6460 RCE
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- CVE.org record CVE-2026-116314 cve.org
- NVD entry CVE-2026-116314 nvd.nist.gov
Other references from the CVE record and advisory
- postgresql.org postgresql.org