Covert Timing Channel in PostgreSQL (CVE-2026-6478)
Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.
AI Analysis
Technical Summary
This vulnerability in PostgreSQL arises from a covert timing channel in the MD5 password comparison mechanism used during authentication. An attacker can exploit this timing discrepancy to recover user credentials, enabling authentication as that user. The issue specifically affects MD5-hashed passwords, which may persist in databases upgraded from PostgreSQL 13 or earlier. The vulnerability does not impact scram-sha-256 password authentication, which is the default in all supported PostgreSQL versions. Affected versions include those prior to PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23. Red Hat has issued security advisories and updates addressing this vulnerability, with patched versions available.
Potential Impact
The vulnerability allows an attacker to recover user credentials through a covert timing channel in the MD5 password comparison process. This can lead to unauthorized authentication as the targeted user. The impact is limited to systems using MD5-hashed passwords, which are legacy from upgrades prior to PostgreSQL 14. Systems using the default scram-sha-256 password method are not affected. The CVSS v3.1 base score is 6.5, indicating a medium severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts on confidentiality and integrity but not availability.
Mitigation Recommendations
Red Hat has released security updates that fix this vulnerability in PostgreSQL versions 18.4, 17.10, 16.14, 15.18, and 14.23. Users should apply these official patches to remediate the issue. Since this vulnerability only affects MD5-hashed passwords, migrating to scram-sha-256 password authentication, which is the default in supported releases, also mitigates the risk. Patch status is confirmed by Red Hat advisories. No additional action is required beyond applying the updates and migrating password hashes where applicable.
Covert Timing Channel in PostgreSQL (CVE-2026-6478)
Description
Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover user credentials sufficient to authenticate. This does not affect scram-sha-256 passwords, the default in all supported releases. However, current databases may have MD5-hashed passwords originating in upgrades from PostgreSQL 13 or earlier. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.
CVSS v3.1
Score 6.5medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability in PostgreSQL arises from a covert timing channel in the MD5 password comparison mechanism used during authentication. An attacker can exploit this timing discrepancy to recover user credentials, enabling authentication as that user. The issue specifically affects MD5-hashed passwords, which may persist in databases upgraded from PostgreSQL 13 or earlier. The vulnerability does not impact scram-sha-256 password authentication, which is the default in all supported PostgreSQL versions. Affected versions include those prior to PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23. Red Hat has issued security advisories and updates addressing this vulnerability, with patched versions available.
Potential Impact
The vulnerability allows an attacker to recover user credentials through a covert timing channel in the MD5 password comparison process. This can lead to unauthorized authentication as the targeted user. The impact is limited to systems using MD5-hashed passwords, which are legacy from upgrades prior to PostgreSQL 14. Systems using the default scram-sha-256 password method are not affected. The CVSS v3.1 base score is 6.5, indicating a medium severity with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts on confidentiality and integrity but not availability.
Mitigation Recommendations
Red Hat has released security updates that fix this vulnerability in PostgreSQL versions 18.4, 17.10, 16.14, 15.18, and 14.23. Users should apply these official patches to remediate the issue. Since this vulnerability only affects MD5-hashed passwords, migrating to scram-sha-256 password authentication, which is the default in supported releases, also mitigates the risk. Patch status is confirmed by Red Hat advisories. No additional action is required beyond applying the updates and migrating password hashes where applicable.
Technical Details
- Gcve Source
- db.gcve.eu
- Csaf Category
- csaf_security_advisory
- Csaf Version
- 2.0
- Publisher
- Red Hat Product Security
- Advisory Id
- RHSA-2026:28208
- Cve Count
- 1
- Additional Cves
- []
- Cvss Version
- null
Threat ID: 6a3aab53eed863c81e3a37ed
Added to database: 06/23/2026, 15:50:43 UTC
Last enriched: 07/01/2026, 00:55:09 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 93
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.