| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 1.56 |
Summary
A vulnerability classified as problematic has been found in PostgreSQL up to 14.23/15.18/16.14/17.10/18.4. This issue affects some unknown processing of the component pg_dump. This manipulation causes heap-based overflow. This vulnerability is tracked as CVE-2026-19385. The attack is restricted to local execution. No exploit exists.
Details
A vulnerability was found in PostgreSQL up to 14.23/15.18/16.14/17.10/18.4. It has been declared as problematic. Affected by this vulnerability is some unknown processing of the component pg_dump. The manipulation with an unknown input leads to a heap-based overflow vulnerability. The CWE definition for the vulnerability is 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(). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at postgresql.org. This vulnerability is known as CVE-2026-19385 since 08/09/2026. The exploitation appears to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 14.24, 15.19, 16.15, 17.11 or 18.5 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 14.0
- 14.1
- 14.2
- 14.3
- 14.4
- 14.5
- 14.6
- 14.7
- 14.8
- 14.9
- 14.10
- 14.11
- 14.12
- 14.13
- 14.14
- 14.15
- 14.16
- 14.17
- 14.18
- 14.19
- 14.20
- 14.21
- 14.22
- 14.23
- 15.0
- 15.1
- 15.2
- 15.3
- 15.4
- 15.5
- 15.6
- 15.7
- 15.8
- 15.9
- 15.10
- 15.11
- 15.12
- 15.13
- 15.14
- 15.15
- 15.16
- 15.17
- 15.18
- 16.0
- 16.1
- 16.2
- 16.3
- 16.4
- 16.5
- 16.6
- 16.7
- 16.8
- 16.9
- 16.10
- 16.11
- 16.12
- 16.13
- 16.14
- 17.0
- 17.1
- 17.2
- 17.3
- 17.4
- 17.5
- 17.6
- 17.7
- 17.8
- 17.9
- 17.10
- 18.0
- 18.1
- 18.2
- 18.3
- 18.4
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PostgreSQL 14.24/15.19/16.15/17.11/18.5
Timeline
08/09/2026 CVE reserved08/13/2026 Advisory disclosed
08/13/2026 VulDB entry created
08/13/2026 VulDB entry last update
Sources
Product: postgresql.orgAdvisory: postgresql.org
Status: Confirmed
CVE: CVE-2026-19385 (🔒)
GCVE (CVE): GCVE-0-2026-19385
GCVE (VulDB): GCVE-100-389437
Entry
Created: 08/13/2026 15:52Changes: 08/13/2026 15:52 (54)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.