CVE-2026-125323: pgEdge control-plane · Missing Authentication for Critical Functionality
Affects pgEdge control-planeSource CVE Database V5
Not known to be exploited · CVSS 7.8 High : upgrade to 0.11.0 soon.
Data as of 10 Nov 2026, 18:04 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.8 |
|---|
- Patch
- Available – fixed in 0.11.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade pgEdge control-plane to 0.11.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pgEdgecontrol-plane | Affected
| Fixed in
|
Description
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.
References
- github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25 (opens in a new tab)
- github.com/pgEdge/control-plane/pull/470 (opens in a new tab)
- github.com/pgEdge/control-plane/commit/88659f7388fc6c86125e60475aa83810171145b7 (opens in a new tab)
- github.com/pgEdge/control-plane/blob/main/changes/v0.11.0.md (opens in a new tab)
- github.com/pgEdge/control-plane/releases/tag/v0.11.0 (opens in a new tab)