Skip to content
Threat Brief

← All advisories

CVE-2026-116328

High 8.8No known exploitationFix available

PostgreSQL generation memory context integer wraparound executes arbitrary code

Record last updated

CVSS score

8.8

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.6%

Higher than 49% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Integer wraparound in PostgreSQL generation memory contexts allows a database user to execute arbitrary code as the operating system user running the database, via freeing an allocation larger than 1 GB and causing its block to be reused for smaller chunks whose back-pointer offset cannot represent that position. Within major versions 16-18, minor versions before PostgreSQL 18.7, 17.12, and 16.16 are affected. Versions before PostgreSQL 16 are unaffected.

Weakness: CWE-190

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
Microsoftazl3 postgresql 16.15-1 on Azure Linux 3.0Not documented16.16-1Microsoft MSRC
Microsoftazl4 postgresql16 16.15-5.azl4 on Azure Linux 4.0Not documented0:16.16-6.azl4Microsoft MSRC
Microsoftazl4 postgresql17 17.11-5.azl4 on Azure Linux 4.0Not documentedNot documentedMicrosoft MSRC
Microsoftazl4 postgresql18 18.6-5.azl4 on Azure Linux 4.0Not documentedNot documentedMicrosoft MSRC

Timeline

  1. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  2. Advisory change

    Microsoft advisory revised (2.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  3. Advisory change

    Microsoft advisory revised (3.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  4. Advisory change

    Microsoft advisory revised (4.0): Information published.

    Source: Microsoft MSRC (opens in a new tab)

  5. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references