CVE-2026-125323: Control Plane auth bypass in pg

Summary

Under the systemd orchestrator, pgEdge Control Plane 0.1.0 through 0.10.1 generates PostgreSQL authentication rules that trust local Unix-socket and loopback connections without a password. A local user with any unprivileged operating-system account on a database host can use this to log in as any database role, including the superuser, and gain full control of the host's databases.

Read the original 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.

Who should check

Teams running pgEdge Control Plane 0.1.0 through 0.10.1 on systemd or Docker Swarm database hosts, including anyone who uses the pg_hba_conf field.

Not fixed by: Restricting the Unix socket does not close the loopback path.

Read the source excerpt

“pgEdge Control Plane v0.1.0 through v0.10.1, inclusive.”

github.com

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure5/25Specific setups only
Reach?/20Unknown. No tracked technology or package matched
Severity7.8/10CVSS 7.8
No patch0/5No signal

What would change the score

Would score about 63 if added to CISA KEV
Would score about 58 if CISA's SSVC rates exploitation active
Would score about 23 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
Affects pgEdge Control Plane v0.1.0 through v0.10.1 (inclusive). Systemd orchestrator: the database runs on a shared multi-user host, so any local account on that host can connect. Docker Swarm: reaching the entries requires code execution inside the database container.
Upgrade to a fixed version: 0.11.0.
Workaround: On v0.9.0 to v0.10.1, set unix_socket_permissions to 0700 (or 0770 with intended accounts in the postgres group). This closes only the socket path, not loopback.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125323 (pgEdge Control Plane generates pg_hba.conf with trust authentication for local and loopback connections), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125323 (entry last updated 2026-11-10):
Affected:
- pgEdge control-plane: fixed in 0.11.0
Fixed versions: 0.11.0.
Conditions (all must be true for the bug to be hit):
- Affects pgEdge Control Plane v0.1.0 through v0.10.1 (inclusive). (source: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25)
- Systemd orchestrator: the database runs on a shared multi-user host, so any local account on that host can connect. (source: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25)
- Docker Swarm: reaching the entries requires code execution inside the database container. (source: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, low-privilege login, no user action.
Workaround: On v0.9.0 to v0.10.1, set unix_socket_permissions to 0700 (or 0770 with intended accounts in the postgres group). This closes only the socket path, not loopback. (source: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25)
CISA KEV: CVE-2026-125323 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125323 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25
- https://github.com/pgEdge/control-plane/pull/470
- https://github.com/pgEdge/control-plane/commit/88659f7388fc6c86125e60475aa83810171145b7
- https://github.com/pgEdge/control-plane/blob/main/changes/v0.11.0.md
- https://github.com/pgEdge/control-plane/releases/tag/v0.11.0
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-125323
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125323.

Timeline

Nov 10, 2026, 5:52 PM UTCCVE published
Nov 10, 2026, 6:26 PM UTCFirst seen by cve.now

Affected versions

pgEdge control-plane
fixed in 0.11.0

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
GitHub · pgEdge/control-plane · Advisory GHSA-vq9p-w6wv-cr25

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-125323
Record
NVD · CVE-2026-125323

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125323

Is CVE-2026-125323 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

Generated pg_hba.conf files use trust authentication for local and loopback connections, so a connection from the host can reach Postgres without a credential. The advisory says this gives full control of every Postgres database on that host, including superuser actions.Source: github.com

Which versions are affected by CVE-2026-125323?

control-plane: before 0.11.0.Source: cve.now feed data

Am I affected, and how do I check?

Versions v0.1.0 through v0.10.1, inclusive. With the systemd orchestrator, the database runs on a shared multi-user host, so any local account on that host can connect. With Docker Swarm, reaching these entries requires code execution inside the database container. Check the installed Control Plane version and which orchestrator is configured.Source: github.com

How do I fix CVE-2026-125323?

Upgrade to v0.11.0, where generated pg_hba.conf files no longer contain trust entries. On v0.9.0 to v0.10.1, setting unix_socket_permissions to 0700 (or 0770 with intended accounts in the postgres group) is a workaround, but it closes only the socket path, not loopback.Source: github.com

pgEdge Control Plane generates pg_hba.conf with trust authentication for local and loopback connections