Skip to main content

CVE-2026-54711: CWE-532: Insertion of Sensitive Information into Log File in Aiven-Open pghoard

0
Low
VulnerabilityCVE-2026-54711cvecve-2026-54711cwe-532
Published: 10/23/2026 (10/23/2026, 12:16:38 UTC)
Source: CVE Database V5
Vendor/Project: Aiven-Open
Product: pghoard

Description

A vulnerability in pghoard, a PostgreSQL backup daemon, prior to version 2.7.1 causes sensitive database connection information, including username and password, to be logged at the debug level when using .pgpass. This issue has been fixed in version 2.7.1.

CVSS v4.0

Score 2.4low

Attack Vector
Local
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
Passive
Vuln. Confidentiality
Low
Vuln. Integrity
None
Vuln. Availability
None
Subsq. Confidentiality
None
Subsq. Integrity
None
Subsq. Availability
None
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Affected software

Aiven-Open

pghoard

Affected versions
<2.7.1
GitHub Actionsmore threats →ai
aiven-open/pghoard
pkg:github/aiven-open/pghoard
Affected versions
<2.7.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/23/2026, 12:45:48 UTC

Technical Analysis

CVE-2026-54711 is a CWE-532 vulnerability affecting pghoard versions before 2.7.1. The flaw involves insertion of sensitive information such as database usernames and passwords into log files at debug level when .pgpass is used for authentication. This could expose credentials to anyone with access to debug logs. The vulnerability was patched in version 2.7.1 to prevent logging of these sensitive details.

Potential Impact

The vulnerability may lead to exposure of database credentials in debug logs, potentially allowing unauthorized users with access to logs to obtain sensitive authentication information. However, the CVSS score of 2.4 and vector indicate low severity with limited attack vector (local), requiring high privileges and user interaction, and low impact on confidentiality and integrity.

Mitigation Recommendations

Upgrade pghoard to version 2.7.1 or later where the issue is patched. Avoid using debug logging in production environments if sensitive information might be logged. Review and secure access to log files to prevent unauthorized viewing.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-06-15T22:58:06.563Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6adb53864d27ba8daa242bbc

Added to database: 10/23/2026, 12:31:02 UTC

Last enriched: 10/23/2026, 12:45:48 UTC

Last updated: 10/23/2026, 13:31:46 UTC

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses