Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8amended

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

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/pgEdge/control-plane 0.11.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.8 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-125323: 0.12% estimated exploitation activity in the next 30 days; percentile 1.97 (FIRST EPSS, 2026-11-14). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Every `pg_hba.conf` generated by the pgEdge Control Plane begins with a hard-coded block of `trust` entries covering Unix-socket and loopback connections. Any operating-system account that can reach the Postgres socket or the loopback interface on a database host can authenticate as any Postgres role, including the superuser, without presenting a credential.

Details The generated file opens with the following six entries: ``` local all all trust host all all 127.0.0.1/32 trust host all all ::1/128 trust local replication all trust host replication all 127.0.0.1/32 trust host replication all ::1/128 trust ``` Postgres evaluates `pg_hba.conf` top-down and stops at the first matching rule. Because these entries are emitted at the top of the file, they also pre-empt every rule below them — including entries supplied by an operator through the `pg_hba_conf` field of a database node specification, which are appended lower in the file and are therefore never reached for…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from osv record GHSA-vq9p-w6wv-cr25

  2. Revision 1 · created ·

    Published from ghsa record GHSA-vq9p-w6wv-cr25

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-125323

Advisory: pgEdge Control Plane generates pg_hba.conf with trust authentication for local and loopback connections
IDs: CVE-2026-125323, GHSA-vq9p-w6wv-cr25
Record: https://patchnext.com/advisories/cve-2026-125323 (revision 2, source checked 13 Nov 2026, 06:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pgEdge/control-plane 0.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pgEdge/control-plane: affected < 0.11.0; fixed in 0.11.0

## Suggested inspection (read-only)
- Go github.com/pgEdge/control-plane: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pgEdge/control-plane.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vq9p-w6wv-cr25 (GitHub-reviewed advisory GHSA-vq9p-w6wv-cr25 lists affected ranges: Go github.com/pgEdge/control-plane >=0 <=0.10.1)
- Verified: https://osv.dev/vulnerability/GHSA-vq9p-w6wv-cr25 (OSV record GHSA-vq9p-w6wv-cr25 lists affected ranges: Go github.com/pgEdge/control-plane >=0 <0.11.0 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…