Skip to content
VulniPulse
High8.8Red Hat Linux

High [CVE-2026-16238] Arbitrary code execution via type confusion in pg_restore_attribute_stats

This high-severity Red Hat Linux advisory covers CVE-2026-16238 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 9, Red Hat package: postgresql18.

CVE-2026-16238 Published Aug 13, 2026Updated by vendor Aug 13, 2026
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

Type confusion in PostgreSQL pg_restore_attribute_stats() allows an object creator to execute arbitrary code as the operating system user running the database, via conflation of range and multirange values. Within major version 18, minor versions before PostgreSQL 18.5 are affected.

A flaw was found in PostgreSQL. This could lead to a complete compromise of the database system.

Note: Red Hat Enterprise Linux 9.6 and earlier releases do not ship the vulnerable PostgreSQL major version (18.x) and are therefore not affected. Red Hat severity: Important — CVSS 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

Weakness: CWE-843. Red Hat lists Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 6; Red Hat Enterprise Linux 7; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Hardened Images; Self-service automation portal 2 as not affected.

Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: postgresql18.

Affected versions
  • < 18.5

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, restrict the ability to create database objects and perform database restorations to only highly trusted administrative users. This operational control limits the attack surface by ensuring that only authorized personnel can introduce potentially malicious objects into the database environment. Carefully manage user privileges to enforce this restriction.

Official advisory · high-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.