PGHoard: Password written to debug log
CVE-2026-54711
LOWPre-NVD 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: —CVSS: —Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- —
- EG Score
- 0.0(none)
- EPSS
- —
- KEV
- Not listed
Published
June 18, 2026
Last Modified
June 18, 2026
Vendor Advisories for CVE-2026-54711(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 | Fixed in / Patch | Released | Source |
|---|---|---|---|
| pip | pghoard | — | 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)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pghoard | 1.0.0 ... 2.1.0 (9 versions) | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 7× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-05 02:53 UTCGHSA enrichment
- 2026-07-01 19:45 UTCGHSA enrichment
- 2026-06-28 12:38 UTCGHSA enrichment
- 2026-06-25 05:31 UTCGHSA enrichment
- 2026-06-21 22:14 UTCGHSA enrichment
- 2026-06-18 15:07 UTCEG score recompute
- 2026-06-18 15:07 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-17922EG 9.8CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS 94%CRITICAL
- CVE-2018-11716EG 9.8EPSS 96%CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8MEDIUM
- CVE-2018-1117NVD 5.0EG 9.8MEDIUM
- CVE-2018-11320EG 9.8CRITICAL
Frequently asked(3)
What is CVE-2026-54711?
CVE-2026-54711 is a low vulnerability published on June 18, 2026. PGHoard: Password written to debug log Impact When using .pgpass, database connection information including the username and password will be logged at the debug level. Patches Upgrade to version 2.7.1 or greater. Workarounds Filter out debug-level logs. References This issue was discovered by…
When was CVE-2026-54711 disclosed?
CVE-2026-54711 was first published in the National Vulnerability Database on June 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-54711?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54711, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54711
Is Your Infrastructure Affected by CVE-2026-54711?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.