Server-memory corruption via expanding lowercase conversion
Published Feb 12, 2026 · Updated Feb 12, 2026
Heap buffer overflow in PostgreSQL pg_trgm 18.0 through 18.1 allows remote authenticated users to corrupt server memory via crafted text. Trigram generation sizes its destination for the original character count, but locale-aware lowercasing can produce more characters and overrun that allocation. The pg_trgm extension and an expanding lowercase conversion must process attacker-controlled text; byte control is limited, and privilege escalation remains unproven.
Summary
What happened
Heap buffer overflow in PostgreSQL pg_trgm 18.0 through 18.1 allows remote authenticated users to corrupt server memory via crafted text. Trigram generation sizes its destination for the original character count, but locale-aware lowercasing can produce more characters and overrun that allocation. The pg_trgm extension and an expanding lowercase conversion must process attacker-controlled text; byte control is limited, and privilege escalation remains unproven.
The record
- CVE
- CVE-2026-2007
- Published
- Feb 12, 2026
- Updated
- Feb 12, 2026
- Vendor
- PostgreSQL Global Development Group
- Product
- PostgreSQL
- Classifications
- CWE-122, CWE-120, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2026CVE publishedPublication date reported by the CVE source.
- Feb 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=18 <18.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo