CVE-2026-116321: PostgreSQL · Improper Null Termination
Affects PostgreSQLSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium · fixed in 18.7 : update PostgreSQL when convenient.
Data as of 12 Nov 2026, 14:48 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 4.3 |
|---|
- Patch
- Available – fixed in 18.7, 17.12, 16.16 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation 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
Upgrading PostgreSQL to versions 18.7, 17.12, 16.16, 15.20, or 14.25 or later will remediate this vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-116321 is a vulnerability in PostgreSQL involving improper null termination during array element assignment. This flaw allows a database user to disclose server memory by manipulating the final byte of a fixed-length name value, which is then treated as a C string. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.