# CVE-2026-104947: 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().


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-wmcm-w9hg-7hch

## What is CVE-2026-104947?

CVE-2026-104947 is a medium-severity vulnerability in EnterpriseDB WarehousePG, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-104947?


## How do I fix CVE-2026-104947?

No fix has been published for CVE-2026-104947 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104947 being exploited?

There is no known exploitation of CVE-2026-104947 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104947 and fix it if it is affected.

What it is: CVE-2026-104947 is a medium-severity vulnerability in EnterpriseDB WarehousePG, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-104947 in the wild and no public exploit code.

Affected product: EnterpriseDB WarehousePG. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104947/ (Markdown: https://insights.sbomify.com/CVE-2026-104947/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104947
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104947
- OSV: https://osv.dev/vulnerability/CVE-2026-104947

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104947/
Summaries are generated and may contain mistakes; the official description above is the record.