CVE-2026-116331
🟡 LowPostgreSQL · 18 before 18.7, 17 before 17.12, 16 before 16.16, 15 before 15.20, 14 before 14.25 (the record lists the 14 line from version "0", likely a data error)
CVSS (Koffei note)
8.8CVSS (v3.1, CVE List)
8.8EPSS (2026-11-18)
0.590%48.95th percentile
Exploitation
No — no exploitation reported (The Hacker News, 19/11/2026); not in KEV; CISA-ADP SSVC exploitation none, automatable no, technical impact total (12/11/2026); not in the 0day sheet (checked 19/11/2026). Found by Zheng Yu (Depthfirst), who demonstrated code execution from low-privilege grants such as TEMPORARY; no public PoC was confirmed in this run (sploitus not checked). Rated 🟡 on CVSS 8.8 with no exploitation or public PoC. cyberveille: site in maintenance on 19/11/2026, not checked
Timeline
- 12/11/2026CVE record published (CVE List)
- 19/11/2026Low-privilege database accounts reach code execution in PostgreSQL, MySQL and Oracle Database
Risk
8.8 High (v3.1, PostgreSQL CNA) — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, EPSS 0.590% (48.95th percentile, scored 18/11/2026); no ADP score (CWE-843 type confusion in the min/max aggregate optimisation: a role that can create temporary objects, or objects in at least one schema, defines a user-defined aggregate with the
SORTOP option and runs arbitrary code as the database's OS user)Fix
Yes — 18.7, 17.12, 16.16, 15.20, 14.25 (12/11/2026, PostgreSQL advisory); also remove the TEMPORARY privilege from roles that do not need it
Official description
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-843