Security News cve security-updates
SEC News High

PostgreSQL fixes type confusion in min/max aggregate optimization

CVE-2026-116331 is a type confusion in PostgreSQL's min/max aggregate optimization that allows an object creator to execute code as the database's operating system user.

KT Kusal Tharindu

PostgreSQL has published a fix for CVE-2026-116331, a type confusion in the min/max aggregate optimization that allows an object creator to execute arbitrary code as the operating system user running the database. The CVSS base score is 8.8 (HIGH), and the weakness is classified as CWE-843, type confusion. The record was published on November 12, 2026.

What is affected

Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. The affected component is the min/max aggregate optimization, and the flaw is reachable by an object creator.

Why it matters

Exploitation runs code as the operating system user that runs the database. The fix disallows these aggregate declarations in the master branch and adds a plan-time check in released branches, so a plan is not generated when the types do not match. The CISA Stakeholder-Specific Vulnerability Categorization (SSVC) assessment lists exploitation as none and automatable as no.

What to do

Upgrade to the fixed release for your branch: the affected ranges end at 18.7, 17.12, 16.16, 15.20, and 14.25. PostgreSQL 14.25 is listed as fixing CVE-2026-116331. Administrators on any of the affected branches need the release that ends their branch’s range.

Sources

  1. NVD: CVE-2026-116331
  2. PostgreSQL: Release Notes
  3. PostgreSQL min/max aggregate type confusion executes arbitrary code
3 posts

Discussion

Spotted an error? Send corrections to [email protected] .

Search Oxelan Signal

Type to search the archive.

Search by title, tag, summary or body text.