CVE-2026-14676
Received Received - Intake

Heap Buffer Overflow in PostgreSQL pg_stat_statements

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: PostgreSQL

Description
Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.5 are affected. Versions before PostgreSQL 18 are unaffected.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-14676
EUVD
EUVD-2026-57840

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
postgresql pg_stat_statements From 18.0 (inc) to 18.5 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions

Instant insights powered by AI
Executive Summary

This is a heap buffer overflow vulnerability in PostgreSQL's pg_stat_statements extension. It allows a query author to execute arbitrary code with the privileges of the operating system user running the database by submitting specially crafted queries containing array constants.

Detection Guidance

To detect this vulnerability, check the PostgreSQL version running on your system. If you are using PostgreSQL version 18 and the version is below 18.5, the system is vulnerable. Run the command: psql --version to check the version. Also, verify if the pg_stat_statements extension is enabled by running: SELECT * FROM pg_extension WHERE extname = 'pg_stat_statements'; in a PostgreSQL client.

If the version is 18.x and below 18.5, or if the extension is enabled on an affected version, the system is vulnerable.

Impact Analysis

An attacker could exploit this to run malicious code on the database server, potentially leading to data theft, system compromise, or disruption of database services. The impact includes unauthorized code execution, data confidentiality breaches, and system integrity violations.

Compliance Impact

This vulnerability could lead to unauthorized access or data breaches, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. Compliance may be compromised due to potential exposure of sensitive data.

Mitigation Strategies

Immediately upgrade PostgreSQL to version 18.5 or later. This can be done by downloading the latest version from the official PostgreSQL website and following the upgrade instructions for your operating system.

If upgrading is not immediately possible, disable the pg_stat_statements extension by running: DROP EXTENSION pg_stat_statements; in a PostgreSQL client. This will prevent exploitation but may impact monitoring capabilities.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-14676. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart