CVE-2026-116331: PostgreSQL · Type Confusion
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 +2
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 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: PostgreSQL 14.25, 15.20, 16.16, 17.12, and 18.7. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigation or workaround is indicated. Patch status is confirmed by the vendor's fixed versions.
Description
CVE-2026-116331 is a high-severity type confusion vulnerability in PostgreSQL's min/max aggregate optimization. It allows an object creator to execute arbitrary code with the privileges of the operating system user running the database. The flaw arises when a user-defined aggregate uses the SORTOP option, causing the query planner to incorrectly treat the aggregate's input and result as the same type when they differ. Versions prior to PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.