EnterpriseDB WarehousePG up to 6.27.6/7.6.0 gp_expand_lock_catalog/gp_expand_bump_version authorization

Summaryinfo

A vulnerability, which was classified as problematic, has been found in EnterpriseDB WarehousePG up to 6.27.6/7.6.0. This affects the function gp_expand_lock_catalog/gp_expand_bump_version. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-104948. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in EnterpriseDB WarehousePG up to 6.27.6/7.6.0. It has been rated as problematic. This issue affects the function gp_expand_lock_catalog/gp_expand_bump_version. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is availability. The summary by CVE is:

WarehousePG (WHPG) 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 are affected by a missing authorization vulnerability (CWE-862) in the built-in cluster expansion functions gp_expand_lock_catalog() and gp_expand_bump_version(). Any authenticated database role can run them, and neither checks privileges. A low-privileged user can call gp_expand_lock_catalog() inside an open transaction to block all catalog changes across the cluster for every user, superusers included, until that transaction ends, which in practice requires a superuser to terminate the session. Blocked changes include DDL, temporary table creation, GRANT and CREATE ROLE. The same user can call gp_expand_bump_version() repeatedly. Each call disconnects sessions that hold temporary tables, with a FATAL error on their next catalog change, and makes every other session rebuild its segment connections.

The advisory is shared at enterprisedb.com. The identification of this vulnerability is CVE-2026-104948 since 10/02/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.

Upgrading to version 6.27.7 or 7.6.1 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• EnterpriseDB

Name

• WarehousePG

Version

• 6.27.0
• 6.27.1
• 6.27.2
• 6.27.3
• 6.27.4
• 6.27.5
• 6.27.6
• 7.0
• 7.1
• 7.2
• 7.3
• 7.4
• 7.5
• 7.6.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion