Heap Buffer Overflow in PostgreSQL Affects Multiple Versions
CVE-2026-14669

8.8HIGH

Key Information:

Vendor

PostgreSQL

Vendor
CVE Published:
13 August 2026

Badges

πŸ“ˆ TrendedπŸ“ˆ Score: 2,200

What is CVE-2026-14669?

CVE-2026-14669 is a heap buffer overflow vulnerability identified within certain versions of the PostgreSQL database management system. PostgreSQL is a widely used open-source relational database known for its reliability, robustness, and strong community support. This specific vulnerability affects functions related to the conversion of timestamp data types, particularly the to_char(timestamptz) function. By manipulating the timezone parameter, a malicious user can execute arbitrary code with the privileges of the database server's operating system user. This can lead to severe consequences for organizations that rely on PostgreSQL for critical data operations, as it can potentially compromise their entire database environment.

Versions prior to PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are vulnerable, emphasizing the need for timely updates and patches. Failure to address this vulnerability can leave organizations exposed to significant security risks.

Potential impact of CVE-2026-14669

  1. Arbitrary Code Execution: The vulnerability allows attackers to execute arbitrary code with the same privileges as the PostgreSQL server, which can lead to full control over the database system. This type of access can facilitate further attacks within the organization's network.

  2. Data Breaches: Given PostgreSQL's use in handling sensitive data, exploitation of this vulnerability poses a high risk of data breaches. Attackers could extract, alter, or delete critical information, resulting in data loss and potential regulatory impacts.

  3. Operational Disruption: Organizations relying on PostgreSQL for day-to-day operations may face significant disruptions if the database is compromised. Such incidents can lead to downtime, loss of productivity, and reputational damage, as well as potential financial losses associated with restoring services and safeguarding data.

Affected Version(s)

PostgreSQL 18 < 18.6

PostgreSQL 17 < 17.11

PostgreSQL 16 < 16.15

References

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

  • πŸ“ˆ

    Vulnerability started trending

  • Vulnerability published

  • Vulnerability Reserved

Credit

The PostgreSQL project thanks Hcamael, Amjad Shahzad, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem.
.