<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 16 Nov 2026 21:48:15 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-54711</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-54711</link>
      <description>&lt;p&gt;pghoard is a PostgreSQL backup daemon and restore tooling that stores backup data in cloud object stores. Prior to version 2.7.1, when using .pgpass, database connection information including the username and password will be logged at the debug level. This issue has been patched in version 2.7.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pghoard is a PostgreSQL backup daemon and restore tooling that stores backup data in cloud object stores. Prior to version 2.7.1, when using .pgpass, database connection information including the username and password will be logged at the debug level. This issue has been patched in version 2.7.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-54711</guid>
    </item>
    <item>
      <title>GHSA-mpx4-jmpr-vm8v — PGHoard: Password written to debug log</title>
      <link>https://db.gcve.eu/vuln/ghsa-mpx4-jmpr-vm8v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pghoard&lt;/p&gt;
&lt;p&gt;### Impact
When using .pgpass, database connection information including the username and password will be logged at the debug level.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version 2.7.1 or greater.&lt;/p&gt;
&lt;p&gt;### Workarounds
Filter out debug-level logs.&lt;/p&gt;
&lt;p&gt;### References
This issue was discovered by BugCrowd user DRAKOKORIAN.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pghoard&lt;/p&gt;
&lt;p&gt;### Impact
When using .pgpass, database connection information including the username and password will be logged at the debug level.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version 2.7.1 or greater.&lt;/p&gt;
&lt;p&gt;### Workarounds
Filter out debug-level logs.&lt;/p&gt;
&lt;p&gt;### References
This issue was discovered by BugCrowd user DRAKOKORIAN.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-mpx4-jmpr-vm8v</guid>
    </item>
    <item>
      <title>PYSEC-2026-2872 — PGHoard: Password written to debug log</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-2872</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pghoard&lt;/p&gt;
&lt;p&gt;### Impact
When using .pgpass, database connection information including the username and password will be logged at the debug level.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version 2.7.1 or greater.&lt;/p&gt;
&lt;p&gt;### Workarounds
Filter out debug-level logs.&lt;/p&gt;
&lt;p&gt;### References
This issue was discovered by BugCrowd user DRAKOKORIAN.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: pghoard&lt;/p&gt;
&lt;p&gt;### Impact
When using .pgpass, database connection information including the username and password will be logged at the debug level.&lt;/p&gt;
&lt;p&gt;### Patches
Upgrade to version 2.7.1 or greater.&lt;/p&gt;
&lt;p&gt;### Workarounds
Filter out debug-level logs.&lt;/p&gt;
&lt;p&gt;### References
This issue was discovered by BugCrowd user DRAKOKORIAN.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-2872</guid>
    </item>
  </channel>
</rss>
