---
id: "CVE-2026-125323"
page: "https://infrastack.ai/live/CVE-2026-125323"
kind: "vulnerability"
aliases: ["CVE-2026-125323"]
title: "pgEdge Control Plane: generated database access rules let local users bypass passwords"
severity: "high"
cvss: 7.8
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: [{"name": "pgEdge Control Plane", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["infrastructure", "pgedge", "postgresql", "self-hosted", "systemd"]
not_affected_if: ["docker-swarm-only", "not-using-control-plane"]
published_at: "2026-11-10T18:17:33+00:00"
first_seen_at: "2026-11-10T18:22:56+00:00"
updated_at: "2026-11-10T18:24:31+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-125323", "first_seen_at": "2026-11-10T18:22:56+00:00"}]
exploit_sources: []
---

# pgEdge Control Plane: generated database access rules let local users bypass passwords

Link for people: https://infrastack.ai/live/CVE-2026-125323 (this .md is for agents)

pgEdge Control Plane versions 0.1.0 through 0.10.1 generate PostgreSQL access files that start with trust entries for local socket and loopback connections, and those entries override operator-set rules. Under the systemd orchestrator, any unprivileged operating-system account on a database host can log in as any PostgreSQL role, including the superuser, without a password.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:pgEdge Control Plane affected range not listed fixed no fixed version listed

## How to check

- Check the installed Control Plane version and whether it is `0.10.1` or earlier.
- Confirm which orchestrator is in use: systemd or Docker Swarm.
- Inspect the generated `pg_hba.conf` for `trust` entries on Unix-socket and loopback lines placed above custom rules.

## Fix

- pgEdge Control Plane: move to `0.11.0`.

## Timeline

- 2026-11-10T18:22:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-125323

## Documents

- [advisory] Vendor advisory: github.com https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25
- [fix] Patch: github.com https://github.com/pgEdge/control-plane/commit/88659f7388fc6c86125e60475aa83810171145b7
- [fix] Release notes: github.com https://github.com/pgEdge/control-plane/releases/tag/v0.11.0

## From the sources

pgEdge Control Plane is a distributed application for managing and orchestrating Postgres databases across multiple hosts. From 0.1.0 to 0.10.1, generated pg_hba.conf files began with hard-coded trust entries for Unix-socket and loopback connections. Because PostgreSQL evaluates the file from top to bottom, those entries also preempted operator-supplied rules in the pg_hba_conf field. Under the systemd orchestrator, any unprivileged operating-system account on a database host could authenticate as any PostgreSQL role, including the superuser, without credentials and obtain full control of the host's databases. Under Docker Swarm, reaching the container-local socket or loopback interface required code execution inside the database container. Publishing the PostgreSQL port to the host did not expose these trust rules because host connections did not appear to originate from 127.0.0.1 or ::1. This issue is fixed in version 0.11.0.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_