CVE-2026-2007

Modified Modified - Updated After Analysis

Heap Buffer Overflow in PostgreSQL pg_trgm Risks Privilege Escalation

Publication date: 2026-02-12

Last updated on: 2026-06-30

Assigner: PostgreSQL

Description

Heap buffer overflow in PostgreSQL pg_trgm allows a database user to achieve unknown impacts via a crafted input string. The attacker has limited control over the byte patterns to be written, but we have not ruled out the viability of attacks that lead to privilege escalation. PostgreSQL 18.1 and 18.0 are affected.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-02-12

Last Modified

2026-06-30

Generated

2026-07-06

AI Q&A

2026-02-12

EPSS Evaluated

2026-07-05

NVD

CVE-2026-2007

EUVD

EUVD-2026-7042

Affected Vendors & Products

Vendor	Product	Version / Range
postgresql	postgresql	From 18.0 (inc) to 18.2 (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().
CWE-120	The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.

Attack-Flow Graph

Executive Summary

CVE-2026-2007 is a heap buffer overflow vulnerability in the PostgreSQL pg_trgm extension affecting versions 18.0 and 18.1.

This flaw allows a database user to write crafted input patterns onto server memory with limited control over the byte patterns written.

Although the exact impact is unknown, it could potentially be exploited for privilege escalation.

Impact Analysis

The vulnerability can lead to integrity and availability issues in the affected PostgreSQL server.

An attacker can exploit the heap buffer overflow to write crafted input to server memory.
This may result in privilege escalation, allowing an attacker to gain higher access rights.
The CVSS score indicates a high impact on availability and a low impact on integrity, but no confidentiality impact.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

To mitigate this vulnerability, you should upgrade PostgreSQL to version 18.2 or later, where the heap buffer overflow in the pg_trgm extension has been fixed.

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

0/70