CVE-2026-116314: PostgreSQL · Improper Input Validation
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 18.7 : patch PostgreSQL soon.
Data as of 12 Nov 2026, 14:49 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in 18.7, 17.12, 16.16 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
Fixed versions are available in PostgreSQL releases 14.25, 15.20, 16.16, 17.12, and 18.7. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigations are indicated by the vendor advisory. Applying the official patches is the recommended action.
Description
CVE-2026-116314 is a high-severity vulnerability in PostgreSQL's pg_restore utility caused by improper input validation. It allows an attacker to execute arbitrary code with the privileges of the operating system user running pg_restore by using a specially crafted non-plain archive. This differs from typical SQL injection during restore, as it enables code execution at the OS level. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.