# CVE-2026-125323: pgEdge Control Plane authentication bypass in pg_hba.conf

Source: https://junglewise.ai/threats/cve-2026-125323-pgedge-control-plane-is-a-distributed-application-for-managing  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-125323 · Severity: high · CVSS 7.8 · Published 2026-11-10

pgEdge Control Plane orchestrates PostgreSQL databases across multiple hosts. Versions 0.1.0 through 0.10.1 generated PostgreSQL authentication configuration files with hard-coded trust entries that allowed any local user on the host to connect as any database role, including the superuser, without a password. This effectively gives any unprivileged user on the system full control of all databases managed by that host.

Vendors: [Go](https://junglewise.ai/threats/vendors/go), [pgEdge](https://junglewise.ai/threats/vendors/pgedge).

## Quick answers

**Is CVE-2026-125323 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-125323 being exploited in the wild.

**How severe is CVE-2026-125323?** High severity, with a CVSS score of 7.8, published 10 November 2026.

**Which products and versions are affected?** github.com/pgEdge/control-plane (Go) <= 0.10.1; pgEdge Control Plane 0.1.0 to 0.10.1.

**Is there a fix for CVE-2026-125323?** Yes: fixed in 0.11.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-125323 attacked?** It is attacked with local access or from the adjacent network.

**Am I affected by CVE-2026-125323?** Check whether you run github.com/pgEdge/control-plane (Go) or pgEdge Control Plane 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.

## How to fix

- Fixed in 0.11.0

## Technical details

The vulnerability arises from hard-coded trust authentication entries at the top of generated pg_hba.conf files for Unix-socket and loopback connections. Since PostgreSQL evaluates authentication rules top-to-bottom, these entries preempt any operator-supplied authentication rules, allowing local and loopback connections without password verification. Under systemd orchestration, any OS account can connect; under Docker Swarm, exploitation requires code execution within the container. The fix in 0.11.0 switches to peer/certificate authentication for local connections.

## Affected products

- pgEdge Control Plane 0.1.0 to 0.10.1

## Identifiers

- CVE-2026-125323
- GHSA-vq9p-w6wv-cr25

## Timeline

- 2026-11-10: disclosed: CVE-2026-125323 published

## References

- [https://github.com/pgEdge/control-plane/blob/main/changes/v0.11.0.md](https://github.com/pgEdge/control-plane/blob/main/changes/v0.11.0.md)
- [https://github.com/pgEdge/control-plane/commit/88659f7388fc6c86125e60475aa83810171145b7](https://github.com/pgEdge/control-plane/commit/88659f7388fc6c86125e60475aa83810171145b7)