Quick answers
- Is CVE-2026-104947 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104947 being exploited in the wild.
- How severe is CVE-2026-104947?
- Informational severity, published 21 October 2026.
- Which products and versions are affected?
- EnterpriseDB WarehousePG 7.2.1 through 7.6.0.
- Is there a fix for CVE-2026-104947?
- 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-104947 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-104947?
- 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 built-in function gp_log_backend_memory_contexts() in WarehousePG 7.2.1–7.6.0 lacks proper authorization checks (CWE-862), allowing any authenticated database role to call it without GRANT and bypassing PostgreSQL's superuser-only restriction on the underlying function. An authenticated attacker can invoke this function against other sessions to write their memory context details—including cached query plans containing other users' query text—to segment server logs, and repeat the call to generate excessive log output.
Affected products
- EnterpriseDB WarehousePG 7.2.1 through 7.6.0
Timeline
- 2026-10-21: disclosed