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-104949 Overview
CVE-2026-104949 is a missing authorization vulnerability [CWE-862] in WarehousePG (WHPG) that allows low-privileged users to disrupt coordinator standby configuration. The flaw resides in the gp_add_coordinator_standby() function, known as gp_add_master_standby() in WHPG 6 and retained as an alias in WHPG 7. Unlike related segment management functions, this function does not enforce superuser privileges. An attacker with a utility-mode connection can inject a fake standby coordinator entry into gp_segment_configuration, blocking administrators from configuring a real standby until a superuser removes the bogus record.
Critical Impact
A low-privileged database user can prevent administrators from adding a legitimate standby coordinator, degrading cluster high-availability posture. User data is not exposed or modified.
Affected Products
- WarehousePG (WHPG) versions 6.27.1 through 6.27.6
- WarehousePG (WHPG) versions 7.2.1 through 7.6.0
- EnterpriseDB distributions bundling the affected WHPG releases
Discovery Timeline
- 2026-10-21 - CVE-2026-104949 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-104949
Vulnerability Analysis
WarehousePG exposes administrative routines for managing cluster topology, including adding and removing segment and coordinator entries. These functions normally require superuser privileges because they modify the authoritative gp_segment_configuration catalog. The function gp_add_coordinator_standby() (aliased as gp_add_master_standby() in WHPG 7 for backward compatibility) omits the superuser check present on its sibling routines. Any role that can establish a utility-mode connection to the cluster can invoke it.
When the function runs against a cluster that has no standby coordinator configured, it writes a new standby entry into gp_segment_configuration without validating that the invoking role is authorized. The entry does not correspond to a real standby host, but the catalog treats it as the configured standby. Subsequent attempts by administrators to add a legitimate standby coordinator fail because the catalog reports one is already present.
Root Cause
The root cause is a missing privilege check inside gp_add_coordinator_standby(). Analogous functions perform an explicit superuser verification before mutating cluster catalogs, but this path does not. The result is a broken access control condition where a user with only connection privileges can modify high-availability metadata.
Attack Vector
Exploitation requires network reachability to the WHPG coordinator and a valid low-privileged database account with permission to open a utility-mode session. The attacker calls the vulnerable function with crafted parameters, inserting an attacker-controlled row into gp_segment_configuration. Recovery requires a superuser to manually delete the fake entry before standby configuration can proceed. There is no path to data exfiltration or modification through this flaw.
No verified exploit code is publicly available. Refer to the EnterpriseDB Security Advisory CVE-2026-104949 for authoritative technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-104949
Indicators of Compromise
- Unexpected rows in gp_segment_configuration with a role indicating a standby coordinator on clusters where no standby was provisioned
- PostgreSQL or WHPG audit log entries showing invocations of gp_add_coordinator_standby() or gp_add_master_standby() by non-superuser roles
- Administrator reports that attempts to add a real standby coordinator fail because one already exists
Detection Strategies
- Enable statement logging for the coordinator and alert on any call to gp_add_coordinator_standby() or gp_add_master_standby() originating from a role lacking the superuser attribute
- Baseline the contents of gp_segment_configuration and generate differential alerts when standby entries appear outside of change windows
- Correlate utility-mode connections from unexpected client addresses with catalog write activity
Monitoring Recommendations
- Forward WHPG coordinator logs to a centralized analytics platform and retain them for configuration-change forensics
- Monitor the ratio of superuser versus non-superuser calls to administrative segment functions
- Track failed gp_add_coordinator_standby administrative attempts, which may indicate a prior unauthorized insertion
How to Mitigate CVE-2026-104949
Immediate Actions Required
- Audit gp_segment_configuration for standby coordinator rows that were not introduced by an administrator and have a superuser remove any fake entries
- Restrict utility-mode connections to the coordinator at the network layer using pg_hba.conf and firewall rules
- Review and tighten role grants so that only trusted operational accounts can connect to the coordinator in utility mode
Patch Information
Upgrade to a fixed WarehousePG release above the affected ranges of 6.27.1-6.27.6 and 7.2.1-7.6.0. Consult the EnterpriseDB Security Advisory CVE-2026-104949 for the exact fixed versions and upgrade guidance applicable to your distribution.
Workarounds
- Revoke EXECUTE on gp_add_coordinator_standby() and its gp_add_master_standby() alias from PUBLIC and from any non-administrative roles
- Limit coordinator connectivity to administrative subnets to reduce the pool of accounts that can reach the vulnerable interface
- Implement scheduled catalog integrity checks that compare gp_segment_configuration to a known-good manifest and alert on drift
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

