Quick answers
- Is CVE-2026-104948 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104948 being exploited in the wild.
- How severe is CVE-2026-104948?
- 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-104948?
- 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-104948 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-104948?
- 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
Two built-in functions, gp_expand_lock_catalog() and gp_expand_bump_version(), lack privilege checks and can be called by any authenticated database role. An attacker can invoke gp_expand_lock_catalog() within a transaction to block catalog modifications cluster-wide, or repeatedly call gp_expand_bump_version() to disconnect sessions holding temporary tables and force segment connection rebuilds, effectively causing denial of service to legitimate users and requiring superuser intervention.
Affected products
- EnterpriseDB WarehousePG 6.27.1 through 6.27.6, 7.2.1 through 7.6.0
Timeline
- 2026-10-21: disclosed