Heap Buffer Overflow in PostgreSQL pgcrypto Affects Multiple Versions
CVE-2026-2005

8.8HIGH

Key Information:

Vendor

PostgreSQL
Status
Postgresql
Vendor
CVE Published:
12 February 2026

Badges

📈 Score: 581👾 Exploit Exists🟡 Public PoC

What is CVE-2026-2005?

CVE-2026-2005 is a critical vulnerability identified in the PostgreSQL pgcrypto extension, which is designed to provide cryptographic functions for secure data handling within PostgreSQL databases. This vulnerability manifests as a heap buffer overflow, allowing an attacker to execute arbitrary code with the privileges of the database's operating system user. Such exploitation can lead to severe consequences for organizations, including unauthorized access to sensitive data, full control over the database environment, and potential breaches extending to the underlying infrastructure. The vulnerability affects various versions of PostgreSQL, specifically those released prior to 18.2, 17.8, 16.12, 15.16, and 14.21, making a significant number of existing deployments at risk if not updated.

Potential impact of CVE-2026-2005

  1. Unauthorized Code Execution: Exploitation of this vulnerability can allow attackers to run malicious code on the server, potentially gaining control over database operations and manipulating or exfiltrating sensitive information.

  2. Data Breach Risks: With elevated privileges, attackers can access and compromise confidential data stored within the database. This could result in severe repercussions for organizations, including legal implications and loss of customer trust.

  3. Infrastructure Compromise: The ability to execute code at the operating system level means that an attacker could exploit the PostgreSQL instance to infiltrate other components of the IT infrastructure, escalating the attack and potentially affecting additional systems and services within the organization.

Affected Version(s)

PostgreSQL 18 < 18.2

PostgreSQL 17 < 17.8

PostgreSQL 16 < 16.12

Exploit Proof of Concept (PoC)

PoC code is written by security researchers to demonstrate the vulnerability can be exploited. PoC code is also a key component for weaponization which could lead to ransomware.

CVE-2026-2005
Created by var77

References

https://www.postgresql.org/support/security/CVE-2026-2005/

CVSS V3.1

Score:
8.8
Severity:
HIGH
Confidentiality:
High
Integrity:
High
Availability:
High
Attack Vector:
Network
Attack Complexity:
Low
Privileges Required:
Low
User Interaction:
None
Scope:
Unchanged

Timeline

  • 🟡

    Public PoC available

  • 👾

    Exploit known to exist

  • Vulnerability published

  • Vulnerability Reserved

Credit

The PostgreSQL project thanks Team Xint Code, as part of zeroday.cloud, for reporting this problem.
.