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.
CVE-2026-125323
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-11-12. A secondary CVSS source baseline 7.8; sources differ by 0.0.
Also known asEUVD-2026-121705 (ENISA EUVD) · GHSA-vq9p-w6wv-cr25 (GitHub Security Advisories)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 1st
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 10, 2026
Last Modified
November 12, 2026
Advisory Details (5)
Auto-updated Nov 10, 2026v0.11.0
Patch available: pgEdge/control-plane v0.11.0
https://github.com/pgEdge/control-plane/releases/tag/v0.11.0control-plane/changes/v0.11.0.md at main · pgEdge/control-plane · GitHub
https://github.com/pgEdge/control-plane/blob/main/changes/v0.11.0.mdcommit 88659f7388fc (pgEdge/control-plane)
Fix landed in pgEdge/control-plane commit 88659f7388fc — awaiting tagged release
https://github.com/pgEdge/control-plane/commit/88659f7388fc6c86125e60475aa83810171145b7fix: use peer/cert auth for local connections
Fix merged in pgEdge/control-plane PR #470 on 2026-09-29 — awaiting tagged release
https://github.com/pgEdge/control-plane/pull/470pgEdge Control Plane generates pg_hba.conf with trust authentication for local and loopback connections · Advisory · pgEdge/control-plane · GitHub
https://github.com/pgEdge/control-plane/security/advisories/GHSA-vq9p-w6wv-cr25Vendor Advisories for CVE-2026-125323(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| go | github.com/pgEdge/control-plane @ 0.11.0 (fixes <= 0.10.1) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| github.com/pgEdge/control-plane | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 22:28 UTCEchelonGraph re-scored
- 2026-11-12 22:28 UTCGHSA enrichmentGHSA-vq9p-w6wv-cr25 · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-11-12 19:29 UTCEchelonGraph re-scored
- 2026-11-12 18:48 UTCEchelonGraph re-scored
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-10 19:00 UTCENISA EUVD ID recordedEUVD-2026-121705 · Source: ENISA EUVD
- 2026-11-10 18:37 UTCEchelonGraph re-scored
- 2026-11-10 18:00 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
- 2026-11-10 17:59 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-125323?
When was the CVE record for CVE-2026-125323 published?
Is CVE-2026-125323 actively exploited?
What is the CVSS score of CVE-2026-125323?
How do I remediate CVE-2026-125323?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-125323
Is Your Infrastructure Affected by CVE-2026-125323?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.