CVE-2026-2007: PostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory

Published Feb 12, 2026
·
Updated

Heap buffer overflow in PostgreSQL pgtrgm 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.

Affected Software

2 affected components
PostgreSQL postgresql>=18.0<=18.1
PostgreSQL postgresql>=18.0<18.2

Event History

Feb 12, 2026
CVE Published
via MITRE·01:00 PM
Data Sourced
via MITRE·01:00 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·02:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-2007?

CVE-2026-2007 is rated as a critical severity vulnerability due to its potential to allow arbitrary memory writes.

2

How do I fix CVE-2026-2007?

To mitigate CVE-2026-2007, upgrade PostgreSQL to version 18.1 or later.

3

Who is affected by CVE-2026-2007?

CVE-2026-2007 affects all PostgreSQL versions from 18.0.

4

What are the potential impacts of CVE-2026-2007?

CVE-2026-2007 could lead to data corruption, service disruptions, or unauthorized access to system memory.

5

What input can trigger CVE-2026-2007?

CVE-2026-2007 can be triggered by a crafted input string to the pg_trgm function in PostgreSQL.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203