PostgreSQL is widely deployed; this RCE as the DB OS user can lead to server compromise and data loss across many organizations.
CVE-2026-16238
PostgreSQL 18 type-confusion allows code execution as the DB OS user
Is CVE-2026-16238 being exploited?
Not confirmed. CVE-2026-16238 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-16238?
CVE-2026-16238 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-16238?
Yes. A fix has been recorded for CVE-2026-16238. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16238 affect?
CVE-2026-16238 affects PostgreSQL 18 (<18.5), pg_restore_attribute_stats(). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16238?
Upgrade to PostgreSQL 18.5 or apply vendor patch; restrict CREATE privileges until patched
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Object creator can execute arbitrary OS commands as the database service user via range/multirange type confusion (remote/authorized user context).
Patch when possible
- affected>= 18 and < 18.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.