CVE-2026-116328: PostgreSQL · Integer Overflow or Wraparound
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:47 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 8.8 |
|---|
- Patch
- Available – fixed in 18.7, 17.12, 16.16
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, 17.12 or 16.16.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
| PostgreSQL | Affected
| Fixed in
|
AI-suggested
Apply the official patches by upgrading PostgreSQL to versions 16.16, 17.12, or 18.7 or later. These versions contain fixes for this vulnerability. No other mitigations are indicated by the vendor advisory.
Description
CVE-2026-116328 is an integer overflow or wraparound vulnerability in PostgreSQL's generation memory contexts. It allows a database user to execute arbitrary code as the operating system user running the database by freeing a large allocation and causing memory corruption. This affects PostgreSQL major versions 16 through 18, specifically versions before 16.16, 17.12, and 18.7. Versions prior to 16 are not affected. The vulnerability has a high severity with a CVSS score of 8.8.