Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege database role
-
ExploitInvoke gp_log_backend_memory_contexts() against other sessions
-
ExecutionSegment backends dump memory contexts to logs
-
ImpactRepeat to flood logs / expose cached plan text
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated database connection with any low-privileged role on WarehousePG 7.2.1 through 7.6.0 (6.x is not affected); no GRANT on gp_log_backend_memory_contexts() and no superuser privileges are needed, so default installations are exploitable by any valid login. The limiting factor is that the attacker must already possess a working database role - there is no unauthenticated path (PR:L) and no user interaction. Realistic risk is therefore concentrated in multi-tenant or shared clusters where low-privilege logins are issued to untrusted users; single-tenant deployments with only trusted roles face little practical exposure. |
| Impact | This is a genuine but modest-priority issue, not a high-impact emergency. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L) scores 5.3 (Medium) and is internally consistent with the description: exploitation is network-reachable but requires an authenticated, low-privileged database role (PR:L), and the only direct scored impact is low availability (VA:L) from log flooding. No confidentiality impact is scored (VC:N) because, per the description, the attacker forces memory-context details into segment server logs the attacker cannot read - so any leakage of other users' cached query plan text benefits a defender/log-reader or a separately privileged party, not the caller directly; this is an indirect confidentiality concern that the CVSS vector deliberately does not credit. No EPSS score, KEV listing, or POC was provided in the input: exploitation status is 'no public exploit identified at time of analysis.' There are no conflicting signals - CVSS, CWE-862 (missing authorization), and the description all agree this is an authorization bypass by an already-authenticated low-privilege user. Net: a legitimately valid finding worth patching in multi-tenant WHPG clusters (where low-privilege roles are untrusted), but low real-world urgency given no exploitation evidence, authentication requirement, and availability-only scored impact. |
| Exploit ScenarioDerived | A multi-tenant WarehousePG cluster grants ordinary analysts low-privilege login roles. One such user repeatedly calls gp_log_backend_memory_contexts() against other sessions - including superuser sessions - forcing their segment backends to dump memory context details (which can contain other users' cached query-plan text) into segment server logs and generating large volumes of log output. No public exploit code was identified at time of analysis; exploitation requires only a valid authenticated database role (PR:L) and no GRANT. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Missing authorization in WarehousePG 7.2.1 through 7.6.0 allows any authenticated, low-privileged database role to call gp_log_backend_memory_contexts() without a GRANT and bypass the superuser-only restriction on PostgreSQL's underlying pg_log_backend_memory_contexts(). An attacker with a valid login can force segment backends for other sessions, including superuser sessions, to write memory-context details such as cached query text into segment server logs they cannot read, and can repeat the call to amplify log volume. No public exploit code or confirmed active exploitation is identified in the provided intelligence, and the assessed impact is limited to low availability loss with no confidentiality or integrity impact within the vulnerable component.
RemediationAI
Patch status in the provided intelligence does not specify an exact fixed release; treat the vendor advisory at https://www.enterprisedb.com/docs/security/advisories/cve2026104947/ as the authoritative source and upgrade affected 7.2.1-7.6.0 installations to the vendor-designated fixed WarehousePG version once confirmed. If an immediate upgrade is not possible, revoke EXECUTE on gp_log_backend_memory_contexts() from PUBLIC and from untrusted or low-privilege roles and grant it only to superusers or tightly controlled administrative accounts, accepting that existing monitoring or diagnostic scripts that call the function may break until they are re-granted. Restrict WarehousePG logins to trusted users and review segment log access so that operators who can read memory-context output are limited, noting that this reduces troubleshooting visibility. Add alerting or rate limits for repeated calls to the function, with the trade-off that aggressive throttling may affect legitimate administrative diagnostics.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
WarehousePG (WHPG) is an Enterprisedb/PostgreSQL-derived data warehouse; the CPE cpe:2.3:a:enterprisedb:warehousepg:*:*:*:*:*:*:*:* identifies the product but does not encode the affected range, which the advisory gives as 7.2.1 through 7.6.0 with 6.x unaffected. CWE-862 (Missing Authorization) applies because the built-in wrapper gp_log_backend_memory_contexts() is executable by any authenticated role without an explicit GRANT, while PostgreSQL restricts pg_log_backend_memory_contexts() to superusers. The wrapper therefore acts as a privilege-boundary bypass: a low-privilege session can force other backends across segments, including superuser sessions, to emit memory-context details that may include query text from cached plans into server logs. The attacker cannot read those logs directly, so the primary security consequence is exposure to log-reading operators plus repeated-call log flooding; the independent assessment scores AV:N/AC:L/PR:L/UI:N/S:U with C:N/I:N/A:L, confirming no direct data read or write and only low availability impact.
Know when Warehousepg gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Network-reachable function callable by any authenticated low-privilege role (PR:L, AC:L); attacker cannot read the leaked logs so C:N, and the scored impact is availability-only log flooding (A:L).
Primary rating from Vendor (EDB).
CVSS VectorVendor: EDB
Lifecycle Timeline
1DescriptionCVE.org
WarehousePG (WHPG) 7.2.1 through 7.6.0 is affected by a missing authorization vulnerability (CWE-862) in the built-in function gp_log_backend_memory_contexts(). Any authenticated database role can run this function without a GRANT. It also gets around the superuser restriction that PostgreSQL places on the underlying pg_log_backend_memory_contexts() function. A low-privileged user can force the segment backends of any other session, superuser sessions included, to write their memory context details to the segment server logs, which the attacker cannot read. Those details can include query text from other users' cached plans, and the call can be repeated to generate large amounts of log output. WarehousePG 6.x is not affected.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Warehousepg
View allMissing authorization in WarehousePG (WHPG) 7.x before 7.6.0-WHPG lets any authenticated database role - with no superus
WarehousePG 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 permits any authenticated database role to invoke built-in clu
WarehousePG 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 allow an authenticated low-privileged user who can open a util
EUVD-2026-107262
GHSA-wmcm-w9hg-7hch
NVD
CVE.org
EPSS
Exploit-DB