PostgreSQL
PostgreSQL min/max aggregate type confusion executes arbitrary code
Type confusion in PostgreSQL min/max aggregate optimization allows an object creator to execute arbitrary code as the operating system user running the database, via a user-defined aggregate whose SORTOP option causes the planner to treat the aggregate's input and result as the same type when they differ. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 18, < 18.7
- >= 17, < 17.12
- >= 16, < 16.16
- >= 15, < 15.20
- < 14.25
Fixed in 18.7, 17.12, 16.16, 15.20, 14.25
Mitigation
Upgrade PostgreSQL to 18.7 or 17.12 or 16.16 or 15.20 or 14.25 or later.
Timeline
Days relative to CVE publicationFirst public PoC 4 days after publication; not in CISA KEV. First PoC: notdenied/CVE-2026-116331-PoC (created 16 Nov 2026, found by us: 16 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| notdenied/CVE-2026-116331-PoC | 16 Nov 2026 +4 d | 16 Nov 2026 | 0 | PoC via PoC Index |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.