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


- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/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-6956-hw8j-vqw3

## What is CVE-2026-104949?

CVE-2026-104949 is a low-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 gp_add_coordinator_standby(). The function is named gp_add_master_standby() in WHPG 6, and WHPG 7 keeps that name as an alias. Unlike the other segment add and remove functions, it does not require superuser privileges. A low-privileged user who can open a utility-mode connection can use it to add a fake standby coordinator entry to gp_segment_configuration on a cluster that has no standby configured. Administrators then cannot add a real standby until a superuser removes the fake entry. User data is not exposed or modified.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-104949 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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