Read the docs

Integer wraparound in PostgreSQL memory contexts allows code execution

Priority MEDIUM 41CWE-190Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Code execution
Confidentiality · integrity · availability
High · High · High
Fix status
Partial Red Hat: 1 fixed, 6 without a fix

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and Red Hat. Impact type from CWE-190 and the CVSS impact.

Summary

PostgreSQL 18 before 18.7, 17 before 17.12 and 16 before 16.16 are affected. An integer wraparound in generation memory contexts lets a freed allocation larger than 1 GB be reused for smaller chunks whose back-pointer offset cannot represent that position (CWE-190). A database user with low privileges can execute arbitrary code as the operating system user running the database.

Written with Claude Haiku 5.5 from the sources below · 2026-11-14

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0059 48th percentileScored 2026-11-16
Fix Partial PostgreSQL: 18.7, 17.12, 16.16Red Hat: 1 advisoryRed Hat: 1 fixed, 6 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
—PostgreSQL18 to before 18.7; 17 to before 17.12; 16 to before 16.1618.7, 17.12, 16.16Patch availableCNA
  • PostgreSQL Vendor— Affected 18 to before 18.7; 17 to before 17.12; 16 to before 16.16 Fixed in 18.7, 17.12, 16.16 Patch available CNA

Remediation

Upgrade PostgreSQL to 18.7, 17.12 or 16.16. Red Hat fixes Red Hat Hardened Images in RHSA-2026:99821. Red Hat lists Red Hat Enterprise Linux 6, 7, 8, 9 and 10 as affected with no fix available.

Written with Claude Haiku 5.5 from the sources below · 2026-11-14

  • Fix · CNA PostgreSQL Fixed in 18.7, 17.12, 16.16

Red Hat 1 advisory

  • RHSA-2026:99821 Released 2026-11-12 · Red Hat rating Important
    Red Hat Hardened Images RPMs bug fix and enhancement update
    • Red Hat Hardened Images libpq-18.7-0.1.hum1@aarch64, libpq-18.7-0.1.hum1@s390x, libpq-18.7-0.1.hum1@src +4

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    PostgreSQL 16.16, 17.12, 18.7

    2 records Highest priority Priority MEDIUM 1 MEDIUM, 1 LOW

    Other records, highest priority first

    • TI-2026-90385 Use-after-free in PostgreSQL pg_show_all_settings() discloses memoryPriority LOW 20

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Enterprise Linux 10AffectedNo fix yet
Red Hat Enterprise Linux 6AffectedNo fix yet
Red Hat Enterprise Linux 7AffectedNo fix yet
Red Hat Enterprise Linux 8AffectedNo fix yet
Red Hat Enterprise Linux 9AffectedNo fix yet
Red Hat Hardened ImagesAffectedNo fix yet
Red Hat Hardened ImagesFixed RHSA-2026:99821

Timeline

  1. 2026-11-12 Threatist record created from CVE-2026-116328
  2. 2026-11-12 Alias added: GHSA-38f3-w39j-87qm
  3. 2026-11-12 Affected versions changed · Red Hat
  4. 2026-11-12 CVSS score added · Red Hat
  5. 2026-11-13 Fix available: Red Hat Hardened Images · Red Hat
  6. 2026-11-13 Fix available: RHSA-2026:99821 · Red Hat
  7. 2026-11-13 CISA SSVC decision points changed
  8. 2026-11-14 Affected versions changed · Red Hat
  9. 2026-11-14 CISA SSVC decision points changed

References

Sources