Skip to main content
Vulnerability Database/CVE-2026-104948

CVE-2026-104948: WarehousePG Privilege Escalation Vulnerability

CVE-2026-104948 is a privilege escalation flaw in WarehousePG versions 6.27.1-6.27.6 and 7.2.1-7.6.0 that allows low-privileged users to block catalog changes cluster-wide. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-104948 Overview

CVE-2026-104948 is a missing authorization vulnerability [CWE-862] affecting WarehousePG (WHPG) versions 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0. The built-in cluster expansion functions gp_expand_lock_catalog() and gp_expand_bump_version() do not verify caller privileges. Any authenticated database role can invoke them. A low-privileged user can block all catalog changes cluster-wide or forcibly disconnect sessions holding temporary tables, degrading availability for every user including superusers.

Critical Impact

Any authenticated WarehousePG user can stall the cluster by locking the catalog in an open transaction or repeatedly bump the catalog version to disconnect sessions, requiring superuser intervention to recover.

Affected Products

  • WarehousePG (WHPG) 6.27.1 through 6.27.6
  • WarehousePG (WHPG) 7.2.1 through 7.6.0
  • EnterpriseDB distributions bundling the affected WHPG releases

Discovery Timeline

  • 2026-10-21 - CVE-2026-104948 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-104948

Vulnerability Analysis

WarehousePG exposes two cluster expansion helper functions, gp_expand_lock_catalog() and gp_expand_bump_version(), intended for use by administrators during online cluster expansion. Neither function performs an authorization check against the invoking role. Any role that can connect to the database can call them directly through SQL.

Calling gp_expand_lock_catalog() inside an open transaction acquires a cluster-wide lock that blocks catalog modifications on every segment. While the transaction remains open, DDL statements, temporary table creation, GRANT, and CREATE ROLE all stall for every user, including superusers. The lock persists until the holding transaction ends, which typically requires a superuser to terminate the offending session.

Calling gp_expand_bump_version() increments the catalog version. Each invocation disconnects any session that currently holds temporary tables with a FATAL error on its next catalog interaction and forces all other sessions to rebuild their segment connections. Repeated calls amplify the disruption without requiring elevated privileges.

Root Cause

The root cause is missing authorization logic in the implementations of gp_expand_lock_catalog() and gp_expand_bump_version(). The functions were designed for administrative use during cluster expansion but lack explicit role or superuser() checks. Their execution privileges default to anyone who can execute the function, which includes every authenticated role.

Attack Vector

An attacker needs only a valid, low-privileged database login over the network. Exploitation requires issuing standard SQL calls:

  • BEGIN; SELECT gp_expand_lock_catalog(); -- hold open to freeze catalog changes cluster-wide.
  • SELECT gp_expand_bump_version(); repeated in a loop to kill sessions and force connection rebuilds.

No client-side tooling, memory corruption, or protocol abuse is required. The attack is purely a logic-level misuse of exposed functions.

Detection Methods for CVE-2026-104948

Indicators of Compromise

  • Audit log entries recording calls to gp_expand_lock_catalog() or gp_expand_bump_version() from roles other than the designated cluster expansion administrator.
  • Long-running transactions holding advisory or catalog locks correlated with stalled DDL across the cluster.
  • Clusters of FATAL disconnect messages affecting sessions that previously created temporary tables.

Detection Strategies

  • Enable pg_stat_statements or statement logging and alert on any execution of the two expansion functions.
  • Monitor pg_locks and pg_stat_activity for sessions holding catalog locks longer than operational baselines.
  • Correlate repeated session terminations with catalog version increments to identify abuse of gp_expand_bump_version().

Monitoring Recommendations

  • Forward WarehousePG audit logs to a centralized analytics platform and build detections for the two function names.
  • Track per-role function call frequency and alert on first-time use by non-administrative roles.
  • Baseline normal DDL latency and alert on cluster-wide stalls that coincide with suspicious transactions.

How to Mitigate CVE-2026-104948

Immediate Actions Required

  • Revoke EXECUTE on gp_expand_lock_catalog() and gp_expand_bump_version() from PUBLIC and restrict to a dedicated expansion role.
  • Audit existing roles for unexpected privileges and remove network access for untrusted accounts.
  • Review recent session termination and catalog lock events for signs of prior abuse.

Patch Information

EnterpriseDB has published a security advisory covering CVE-2026-104948 with fixed release guidance. Upgrade WarehousePG to a release outside the affected 6.27.1 to 6.27.6 and 7.2.1 to 7.6.0 ranges as directed by the EnterpriseDB Security Advisory.

Workarounds

  • Explicitly REVOKE EXECUTE ON FUNCTION gp_expand_lock_catalog(), gp_expand_bump_version() FROM PUBLIC; and GRANT only to administrative roles.
  • Restrict database network exposure using host-based authentication (pg_hba.conf) to limit which roles can connect from untrusted networks.
  • Monitor and automatically terminate sessions that hold catalog locks beyond defined thresholds until patching completes.
bash
# Configuration example
psql -d postgres -c "REVOKE EXECUTE ON FUNCTION gp_expand_lock_catalog() FROM PUBLIC;"
psql -d postgres -c "REVOKE EXECUTE ON FUNCTION gp_expand_bump_version() FROM PUBLIC;"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.