LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.2Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

PostgreSQL 18.0 and 18.1 have a pg_trgm heap buffer overflow where crafted input can write attacker-influenced data into server memory. Reported impacts are not fully characterized; availability impact is high and privilege escalation has not been ruled out.

Executive priority

Prioritize remediation for internet-facing, multi-tenant, or user-search-heavy PostgreSQL 18 deployments. The risk is high because memory corruption can affect database availability and potentially integrity, even though exploitation evidence is not currently shown.

Technical view

CVE-2026-2007 is a CWE-120/CWE-122 heap buffer overflow in PostgreSQL pg_trgm. The CVSS 3.1 score is 8.2, with network, low-complexity, no-user-interaction characteristics. Sources state limited attacker control over written byte patterns and unknown final impact.

Likely exposure

Exposure is mainly PostgreSQL 18.0 and 18.1 deployments, especially where pg_trgm can process user-controlled or tenant-controlled strings. The bundle lists other versions as unaffected by default, but packaged distributions should be checked against vendor advisories.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The description says a database user can trigger it, while the CVSS vector lists no privileges required; treat access conditions as unresolved until vendor guidance clarifies.

Researcher notes

Evidence is limited on exploitability and final impact. Focus validation on affected version confirmation, pg_trgm reachability, role boundaries, and whether distribution packages contain the vendor fix. Do not assume privilege escalation without further vendor evidence.

Mitigation direction

  • Upgrade affected PostgreSQL 18.0 and 18.1 systems using PostgreSQL vendor guidance.
  • Review Red Hat advisories if using Red Hat-packaged PostgreSQL.
  • Limit untrusted database access to pg_trgm-dependent search paths where practical.
  • Monitor PostgreSQL and distribution advisories for clarified impact and fixed builds.

Validation and detection

  • Inventory PostgreSQL versions and flag 18.0 or 18.1 instances.
  • Identify applications using pg_trgm indexes, operators, or similarity functions.
  • Check installed package versions against PostgreSQL and Red Hat advisory status.
  • Review database roles that can submit untrusted strings to pg_trgm workflows.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2007 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H3.94.2PostgreSQL
8.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H3.94.2redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2026-2007Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPpostgresql: PostgreSQL pg_trgm heap buffer overflow writes pattern onto server memory
other:Red Hat severity ratingcvssV3_1
  • 2026-02-12T14:01:16.168Z: Reported to Red Hat.
  • 2026-02-12T13:00:11.127Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aPostgreSQL18unaffected
Weakness

CWE details

CWE-120CWE-122

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.