CVE-2026-2005
Heap Buffer Overflow in PostgreSQL pgcrypto Enables Code Execution
Publication date: 2026-02-12
Last updated on: 2026-02-20
Assigner: PostgreSQL
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| postgresql | postgresql | From 18.0 (inc) to 18.2 (exc) |
| postgresql | postgresql | From 14.0 (inc) to 14.21 (exc) |
| postgresql | postgresql | From 15.0 (inc) to 15.16 (exc) |
| postgresql | postgresql | From 16.0 (inc) to 16.12 (exc) |
| postgresql | postgresql | From 17.0 (inc) to 17.8 (exc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-2005 is a heap buffer overflow vulnerability in the PostgreSQL pgcrypto module.
This flaw allows a ciphertext provider to execute arbitrary code with the privileges of the operating system user running the database.
It affects PostgreSQL versions prior to 18.2, 17.8, 16.12, 15.16, and 14.21.
How can this vulnerability impact me? :
An attacker exploiting this vulnerability can execute arbitrary code on the system with the same privileges as the operating system user running the PostgreSQL database.
This can lead to a full compromise of the database server, including unauthorized access, modification, or deletion of data.
The vulnerability has a high impact on confidentiality, integrity, and availability of the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-2005 vulnerability, users should upgrade PostgreSQL to the fixed versions released on February 12, 2026.
- Upgrade to PostgreSQL version 18.2 or later.
- Upgrade to PostgreSQL version 17.8 or later.
- Upgrade to PostgreSQL version 16.12 or later.
- Upgrade to PostgreSQL version 15.16 or later.
- Upgrade to PostgreSQL version 14.21 or later.