CVE-2026-19385
Received Received - Intake

Heap Buffer Overflow in PostgreSQL pg_dump

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: PostgreSQL

Description
Heap buffer overflow in PostgreSQL pg_dump of long function transform lists allows an object creator to execute arbitrary code as the operating system user running pg_dump, via a crafted transform list. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.

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-19385
EUVD
EUVD-2026-57853

Affected Vendors & Products

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

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a heap buffer overflow vulnerability in PostgreSQL's pg_dump utility. It occurs when pg_dump processes long function transform lists, allowing an attacker who creates a malicious object to execute arbitrary code as the operating system user running pg_dump.

Detection Guidance

To detect this vulnerability, check the version of PostgreSQL installed on your system. Run: pg_dump --version. If the output shows a version before 18.5, 17.11, 16.15, 15.19, or 14.24, your system is vulnerable.

Impact Analysis

An attacker could exploit this to run arbitrary code with the privileges of the user executing pg_dump. This could lead to data theft, system compromise, or further network access if the user has elevated permissions.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating confidentiality and integrity requirements in GDPR and HIPAA. Organizations using affected PostgreSQL versions may face compliance violations if exploited.

Mitigation Strategies

Immediately update PostgreSQL to a patched version: 18.5, 17.11, 16.15, 15.19, or 14.24. After updating, verify the new version with pg_dump --version. Avoid using pg_dump on untrusted databases until patched.

Chat Assistant

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

EPSS Chart