Skip to content
Emerging threatsHigh

CVE-2026-116331Azl3 Postgresql 16.15-1 Type Confusion

PostgreSQL min/max aggregate type confusion executes arbitrary code

Published Nov 12, 2026 · Updated Nov 14, 2026 · Also known as EUVD-2026-124511, GHSA-8qpw-62p2-qh8p

Key Facts

Patch in the next maintenance window
  • CVE-2026-116331 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Azl3 Postgresql 16.15-1 (Microsoft), Azl4 Postgresql16 16.15-5.azl4 (Microsoft), Azl4 Postgresql17 17.11-5.azl4 (Microsoft) and 22 more products.
  • It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
  • EPSS estimates a 0.6% probability of exploitation in the next 30 days.
  • Fixed versions are available, including libpq-main 18.7-0.1.hum1, PostgreSQL 14.25, PostgreSQL 15.20.
  • Brandefense priority: patch in the next maintenance window, because of its high severity, although no exploitation is known.

Scores

CVSS v3.1

8.8

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

0.6%

Higher than 48.9% of all scored CVEs

Exploit maturity

Proof of concept

ATLAS score

41/100

Publication score, see How it works

Exploitation Verdict

KEV listed

Not listed

Federal due date

None

No federal due date

Ransomware use

Not reported

Attributed actors

None named

Exploit & Defence Guidance

Exploit maturity

Proof of concept

Public exploit code

1

Proof-of-concept links

In-the-wild evidence

0

Reports of active use

Advisories And Exploit References

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.

Affected Products

76 affected entries in total
ProductAffected versionsFixed in
Azl3 Postgresql 16.15-1MicrosoftSee advisoryn/a
Azl4 Postgresql16 16.15-5.azl4MicrosoftSee advisoryn/a
Azl4 Postgresql17 17.11-5.azl4MicrosoftSee advisoryn/a
Azl4 Postgresql18 18.6-5.azl4MicrosoftSee advisoryn/a
postgresql15alpineSee advisory15.20-r0
20 more affected products in the full CVE brief

Patched Releases

libpq-main

18.7-0.1.hum1

PostgreSQL

14.25, 15.20, 16.16, 17.12, 18.7

postgresql-15

15.20-0+deb12u1

postgresql-17

17.12-0+deb13u1

postgresql-18

18.7-1

postgresql14

14.25-1.1

postgresql14-contrib

14.25-1.1

postgresql14-devel

14.25-1.1

postgresql14-docs

14.25-1.1

postgresql14-llvmjit

14.25-1.1

postgresql14-llvmjit-devel

14.25-1.1

postgresql14-plperl

14.25-1.1

postgresql14-plpython

14.25-1.1

postgresql14-pltcl

14.25-1.1

postgresql14-server

14.25-1.1

postgresql14-server-devel

14.25-1.1

postgresql14-test

14.25-1.1

postgresql15

15.20-1.1, 15.20-r0

postgresql15-contrib

15.20-1.1

postgresql15-devel

15.20-1.1

postgresql15-docs

15.20-1.1

postgresql15-llvmjit

15.20-1.1

postgresql15-llvmjit-devel

15.20-1.1

postgresql15-plperl

15.20-1.1

postgresql15-plpython

15.20-1.1

Timeline

  1. Publicly disclosed

    Nov 12, 2026

  2. Last updated

    Nov 14, 2026

Weakness Type

  • CWE-843 Access of Resource Using Incompatible Type

FAQ

Common Questions.

Is CVE-2026-116331 On Your Attack Surface?

Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.

Request A Demo

Figures as of Nov 19, 2026. Compiled by Brandefense technologies from public vulnerability catalogs; scoring as described in How it works.

To report an error, contact Brandefense.