CVE-2026-116318: PostgreSQL · SQL Injection
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 18.7 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
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 PostgreSQL to 18.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
Upgrade affected PostgreSQL installations to version 18.7 or later, where this vulnerability is fixed. No other mitigations are indicated or necessary once the patch is applied.
Description
CVE-2026-116318 is a high-severity SQL injection vulnerability in PostgreSQL's pg_dump utility. It allows an object creator to execute arbitrary SQL commands as the user restoring the dump. The issue arises from an inherited column with a child-local not-null constraint whose name requires quoting. This affects PostgreSQL major version 18 prior to minor version 18.7. Versions before 18 are not affected. The vulnerability has been fixed in PostgreSQL 18.7.