Skip to content
Connect AISign inSign up free
CVE-2026-1163318.8High

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

0.6%probability of exploitation in the next 30 days
48th percentile
050100

Higher than 48% of scored CVEs

8.8HighCVSS
LowHigh

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.

ExploitationProof of concept public

Not in CISA KEV as of catalogue 2026.11.18 (18 Nov)

  1. 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.

  1. Seen in Debian’s tracker on 19 Nov: Debian 12 fixed in postgresql-15 15.20-0+deb12u1 (DLA-4905-1) Debian
  2. Seen in Debian’s tracker on 19 Nov: Debian 13 fixed in postgresql-17 17.12-0+deb13u1 (DSA-6625-1) Debian
  3. Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
  4. Red Hat’s tracker lists RHEL 7 as affected, with no fix released Red Hat
  5. Red Hat’s tracker lists RHEL 8 as affected, with no fix released Red Hat
  6. Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
  7. SUSE’s tracker lists openSUSE Leap 16.0 as affected, with no fix released SUSE
  8. SUSE’s tracker lists openSUSE Leap 16.1 as affected, with no fix released SUSE
  9. SUSE’s tracker lists SLES 12 SP5 as affected, with no fix released SUSE
  10. SUSE’s tracker lists SLES 15 SP1 as not affected SUSE
  11. SUSE’s tracker lists SLES 15 SP2 as affected, with no fix released SUSE
  12. SUSE’s tracker lists SLES 15 SP3 as affected, with no fix released SUSE
  13. SUSE’s tracker lists SLES 15 SP4 as affected, with no fix released SUSE
  14. SUSE’s tracker lists SLES 15 SP5 as affected, with no fix released SUSE
  15. SUSE’s tracker lists SLES 15 SP6 as affected, with no fix released SUSE
  16. SUSE’s tracker lists SLES 15 SP7 as affected, with no fix released SUSE
  17. SUSE’s tracker lists SLES 16.0 as affected, with no fix released SUSE
  18. SUSE’s tracker lists SLES 16.1 as affected, with no fix released SUSE
  19. Ubuntu’s tracker lists Ubuntu 14.04 as affected, with no fix released Ubuntu
  20. 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.

New articles also arrive in the RSS feed.

References