CVE-2026-14669

Modified Modified - Updated After Analysis

Heap Buffer Overflow in PostgreSQL to_char(timestamptz)

Publication date: 2026-08-13

Last updated on: 2026-08-29

Assigner: PostgreSQL

Description

Heap buffer overflow in PostgreSQL to_char(timestamptz) allows the party choosing the timezone to execute arbitrary code as the operating system user running the database, via a long POSIX timezone abbreviation. Versions before PostgreSQL 18.6, 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-29

Generated

2026-09-02

AI Q&A

2026-08-13

EPSS Evaluated

2026-09-01

NVD

CVE-2026-14669

EUVD

EUVD-2026-57836

Affected Vendors & Products

Vendor	Product	Version / Range
postgresql	postgresql	From 14.0 (inc) to 14.24 (exc)
postgresql	postgresql	From 15.0 (inc) to 15.19 (exc)
postgresql	postgresql	From 16.0 (inc) to 16.15 (exc)
postgresql	postgresql	From 17.0 (inc) to 17.11 (exc)
postgresql	postgresql	From 18.0 (inc) to 18.5 (exc)

Helpful Resources

Exploitability

CWE

KEV

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

Executive Summary

This is a heap buffer overflow in PostgreSQL's to_char(timestamptz) function. It allows an attacker who can select the timezone to execute arbitrary code with the privileges of the database's operating system user. The issue occurs when a long POSIX timezone abbreviation is used.

Detection Guidance

To detect this vulnerability, check your PostgreSQL version using: psql --version. If your version is 18.5 or earlier, 17.11 or earlier, 16.15 or earlier, 15.19 or earlier, or 14.24 or earlier, your system is vulnerable.

Impact Analysis

An attacker could gain full control over the database server, leading to data theft, manipulation, or system compromise. This could result in unauthorized access to sensitive data, disruption of services, or further network infiltration.

Compliance Impact

This vulnerability could lead to unauthorized data access or modification, violating GDPR's data protection requirements or HIPAA's safeguards for protected health information. Non-compliance may result in legal penalties, fines, or reputational damage.

Mitigation Strategies

Immediately upgrade PostgreSQL to a patched version: 18.6, 17.11, 16.15, 15.19, or 14.24. Avoid using untrusted timezone inputs in to_char(timestamptz) functions until patched.

Hi! I’m here to help you understand CVE-2026-14669. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70