CVE-2026-16238
Received Received - Intake

Type confusion in PostgreSQL pg_restore_attribute_stats()

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: PostgreSQL

Description
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. Versions before PostgreSQL 18 are unaffected.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-16238
EUVD
EUVD-2026-57848

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
postgresql postgresql to 18.5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-843 The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a type confusion vulnerability in PostgreSQL's pg_restore_attribute_stats() function. It allows an object creator to execute arbitrary code as the operating system user running the database by mixing up range and multirange values. Only PostgreSQL version 18 minor versions before 18.5 are affected.

Detection Guidance

Check PostgreSQL version with 'psql --version' or 'SELECT version();'. If running PostgreSQL 18.x before 18.5, the system is vulnerable. Compare installed version against patched releases (18.6, 17.11, 16.15, etc.).

Impact Analysis

An attacker with object creation privileges could exploit this to run malicious code on the database server, potentially stealing data, modifying records, or disrupting services. The high CVSS score (8.8) indicates significant risk if unpatched.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's integrity/confidentiality principles and HIPAA's security rule requirements for protecting health data. Non-compliance risks include fines and legal penalties.

Mitigation Strategies

Upgrade PostgreSQL to a patched version (18.6 or later, 17.11, 16.15, etc.). Restart the database service after upgrade. Review user permissions to limit object creation rights.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-16238. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart