CVE-2026-2007

CVE-2026-2007 is a high-severity vulnerability in Postgresql with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-122.

Key facts

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.

Frequently asked questions

What is CVE-2026-2007?
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.
How severe is CVE-2026-2007?
CVE-2026-2007 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.
Is CVE-2026-2007 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (38th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-2007?
CVE-2026-2007 affects Postgresql. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-2007?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-2007 have an EU (EUVD) identifier?
Yes. CVE-2026-2007 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-7042.
When was CVE-2026-2007 published?
CVE-2026-2007 was published on 2026-02-12 and last updated on 2026-06-30.

References

Affected products (1)

More vulnerabilities in Postgresql

All CVEs affecting Postgresql →

Other CWE-122 (Heap-based Buffer Overflow) vulnerabilities

Browse all CWE-122 (Heap-based Buffer Overflow) vulnerabilities →