CVE-2026-2007
8.2PostgreSQL · pg_trgm
A heap-based buffer overflow exists in the PostgreSQL pg_trgm extension, potentially allowing an attacker to cause a crash or achieve privilege escalation through crafted input strings.
Executive summary
A heap buffer overflow vulnerability in the PostgreSQL pg_trgm extension poses a significant security risk, potentially allowing unauthorized privilege escalation or service disruption.
Vulnerability
This flaw is a heap-based buffer overflow (CWE-122) triggered by sending a crafted input string to the pg_trgm extension. Based on the CVSS vector, this vulnerability is exploitable by an unauthenticated attacker over the network.
Business impact
The vulnerability carries a CVSS score of 8.2, reflecting its potential for high availability impact and unauthorized integrity compromise. Successful exploitation could lead to database service instability or unauthorized escalation of privileges, which may result in full system compromise and significant business disruption.
Remediation
Immediate Action: Review the official PostgreSQL security advisory at the provided reference link and apply the latest security patches to move beyond version 18.1.
Proactive Monitoring: Monitor database server logs for unusual error patterns, unexpected crashes, or unauthorized attempts to leverage the pg_trgm extension functions.
Compensating Controls: Restrict access to the database from untrusted networks and ensure that the pg_trgm extension is only enabled in environments where it is strictly required for business operations.
Exploitation status
Public Exploit Available: exploit_available (unknown)
Analyst recommendation
Given the severity of a heap-based buffer overflow in a core database component, organizations should prioritize patching their PostgreSQL installations. Administrators must verify their current version and update to the latest release provided by the vendor to eliminate this vulnerability.
More PostgreSQL CVEs
Sources
Originally found and disclosed by The PostgreSQL project thanks Heikki Linnakangas for reporting this problem., per the CVE Program record.