# CVE-2026-104948: WarehousePG (WHPG) 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 are affected by a missing authorization vulnerability (CWE-862) in the buil


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/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-7m66-9h4j-25fj

## What is CVE-2026-104948?

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

### Official description

WarehousePG (WHPG) 6.27.1 through 6.27.6 and 7.2.1 through 7.6.0 are affected by a missing authorization vulnerability (CWE-862) in the built-in cluster expansion functions gp_expand_lock_catalog() and gp_expand_bump_version(). Any authenticated database role can run them, and neither checks privileges. A low-privileged user can call gp_expand_lock_catalog() inside an open transaction to block all catalog changes across the cluster for every user, superusers included, until that transaction ends, which in practice requires a superuser to terminate the session. Blocked changes include DDL, temporary table creation, GRANT and CREATE ROLE. The same user can call gp_expand_bump_version() repeatedly. Each call disconnects sessions that hold temporary tables, with a FATAL error on their next catalog change, and makes every other session rebuild its segment connections.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-104948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104948 is a high-severity vulnerability in EnterpriseDB WarehousePG, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-104948 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-104948/ (Markdown: https://insights.sbomify.com/CVE-2026-104948/index.md)
```

## Sources

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

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