CVE-2026-116331: PostgreSQL min/max aggregate type confusion executes arbitrary code
Vendor not yet named
Fixed in Debian 12/13 · Exploitation: public proof of concept (unverified)
At a glance
Higher than 48% of scored CVEs
What it isNVD
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.
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- Red Hat Enterprise Linux 10Affected, no fix releasedchecked 19 Nov 09:00 UTC
- Red Hat Enterprise Linux 9Affected, no fix releasedchecked 19 Nov 09:00 UTC
- Red Hat Enterprise Linux 8Affected, no fix releasedchecked 19 Nov 09:00 UTC
- Ubuntu 26.04Under investigationchecked 19 Nov 09:00 UTC
- Ubuntu 24.04Under investigationchecked 19 Nov 09:00 UTC
- Ubuntu 22.04Under investigationchecked 19 Nov 09:00 UTC
- Debian 13Fixed in postgresql-17 17.12-0+deb13u1 (DSA-6625-1)checked 19 Nov 09:00 UTC
- Debian 12Fixed in postgresql-15 15.20-0+deb12u1 (DLA-4905-1)checked 19 Nov 09:00 UTC
- SUSE Linux Enterprise Server 16.1Affected, no fix releasedchecked 19 Nov 09:00 UTC
- SUSE Linux Enterprise Server 16.0Affected, no fix releasedchecked 19 Nov 09:00 UTC
- SUSE Linux Enterprise Server 15 SP7Affected, no fix releasedchecked 19 Nov 09:00 UTC
- openSUSE Leap 16.1Affected, no fix releasedchecked 19 Nov 09:00 UTC
- openSUSE Leap 16.0Affected, no fix releasedchecked 19 Nov 09:00 UTC
ExploitationProof of concept public
Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)
- Proof of concept public1 public GitHub repository (unverified), listed by PoC-in-GitHub16 Nov
Not seen so far: in CISA KEV · exploited (reported) · scanning observed.
Weakness and public checks
- Public check
- No public nuclei template
- Weakness
- Type Confusion · Memory Corruption
What changed
Debian status tracked since 19 Nov 2026. Red Hat status tracked since 19 Nov 2026. SUSE status tracked since 19 Nov 2026. Ubuntu status tracked since 19 Nov 2026.
- Seen in Debian’s tracker on 19 Nov: Debian 12 fixed in postgresql-15 15.20-0+deb12u1 (DLA-4905-1) Debian
- Seen in Debian’s tracker on 19 Nov: Debian 13 fixed in postgresql-17 17.12-0+deb13u1 (DSA-6625-1) Debian
- Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 7 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 8 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
- SUSE’s tracker lists openSUSE Leap 16.0 as affected, with no fix released SUSE
- SUSE’s tracker lists openSUSE Leap 16.1 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 12 SP5 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP1 as not affected SUSE
- SUSE’s tracker lists SLES 15 SP2 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP3 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP4 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP5 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP6 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP7 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 16.0 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 16.1 as affected, with no fix released SUSE
- Ubuntu’s tracker lists Ubuntu 14.04 as affected, with no fix released Ubuntu
- Ubuntu’s tracker lists Ubuntu 16.04 as under investigation Ubuntu
Showing the latest 20 changes.
Coverage1 article · 1 outlet
First in our coverage: The Hacker News, 19 Nov.
- Researcher Demonstrates RCE Exploits in Four Database EnginesThe Hacker News · first in our coverage
New articles also arrive in the RSS feed.