Quick answers
- Is CVE-2026-104949 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104949 being exploited in the wild.
- How severe is CVE-2026-104949?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- EnterpriseDB WarehousePG 6.27.1 through 6.27.6, 7.2.1 through 7.6.0.
- Is there a fix for CVE-2026-104949?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-104949 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-104949?
- Check whether you run EnterpriseDB WarehousePG at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The gp_add_coordinator_standby() function (and its gp_add_master_standby() alias in version 6) in WarehousePG fails to enforce superuser privilege requirements, unlike other segment add/remove functions. A low-privileged user with utility-mode connection access can invoke this function to insert false entries into gp_segment_configuration, causing a denial of service for legitimate standby configuration. The vulnerability requires local/utility-mode access and does not result in data exposure.
Affected products
- EnterpriseDB WarehousePG 6.27.1 through 6.27.6, 7.2.1 through 7.6.0
Timeline
- 2026-10-21: disclosed