CVE-2026-6478: Covert Timing Channel in PostgreSQL
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
CVE-2026-6478 is a vulnerability in PostgreSQL where a covert timing channel in the comparison of MD5-hashed passwords during authentication can be exploited to recover user credentials. This vulnerability affects PostgreSQL versions before 18.4, 17.10, 16.14, 15.18, and 14.23. The issue does not impact scram-sha-256 password authentication, which is the default in supported releases. The vulnerability is relevant for databases that retain MD5-hashed passwords, often due to upgrades from PostgreSQL 13 or earlier. The CVSS v3.1 base score is 6.5 (medium severity), with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts confidentiality and integrity but not availability. Red Hat has issued security advisories and errata addressing this vulnerability with updated PostgreSQL packages.
Potential Impact
An attacker can exploit the timing channel in MD5 password comparison to recover user credentials sufficient to authenticate to the PostgreSQL database. This compromises confidentiality and integrity of user authentication. The vulnerability does not affect the default scram-sha-256 password method, limiting impact to systems still using MD5-hashed passwords, typically from upgrades. There are no known exploits in the wild at this time.
Mitigation Recommendations
Red Hat has released updated PostgreSQL packages that fix this vulnerability. Users should apply the security updates provided in the Red Hat advisories (e.g., RHSA-2026:27718 and related errata) to remediate the issue. Since the vulnerability does not affect scram-sha-256 passwords, migrating to this authentication method where possible further mitigates risk. Patch status is confirmed via Red Hat advisories; therefore, applying the official updates is the recommended remediation.
CVE-2026-6478: Covert Timing Channel in PostgreSQL
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
pkg:deb/postgresql/postgresqlRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-6478 is a vulnerability in PostgreSQL where a covert timing channel in the comparison of MD5-hashed passwords during authentication can be exploited to recover user credentials. This vulnerability affects PostgreSQL versions before 18.4, 17.10, 16.14, 15.18, and 14.23. The issue does not impact scram-sha-256 password authentication, which is the default in supported releases. The vulnerability is relevant for databases that retain MD5-hashed passwords, often due to upgrades from PostgreSQL 13 or earlier. The CVSS v3.1 base score is 6.5 (medium severity), with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts confidentiality and integrity but not availability. Red Hat has issued security advisories and errata addressing this vulnerability with updated PostgreSQL packages.
Potential Impact
An attacker can exploit the timing channel in MD5 password comparison to recover user credentials sufficient to authenticate to the PostgreSQL database. This compromises confidentiality and integrity of user authentication. The vulnerability does not affect the default scram-sha-256 password method, limiting impact to systems still using MD5-hashed passwords, typically from upgrades. There are no known exploits in the wild at this time.
Mitigation Recommendations
Red Hat has released updated PostgreSQL packages that fix this vulnerability. Users should apply the security updates provided in the Red Hat advisories (e.g., RHSA-2026:27718 and related errata) to remediate the issue. Since the vulnerability does not affect scram-sha-256 passwords, migrating to this authentication method where possible further mitigates risk. Patch status is confirmed via Red Hat advisories; therefore, applying the official updates is the recommended remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-04-17T00:44:57.549Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-6478","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:27718","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:27743","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:27742","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:27738","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:28999","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:28208","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26181","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:28143","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:29815","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:32994","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26561","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:29953","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26524","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:29904","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:32983","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26525","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:29212","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:28037","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26203","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:26204","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:27741","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:21182","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22878","vendor":"Red Hat"}]
Threat ID: 6a05cfe8ec166c07b0e1394a
Added to database: 05/14/2026, 13:36:40 UTC
Last enriched: 07/30/2026, 23:08:06 UTC
Last updated: 07/31/2026, 19:23:00 UTC
Views: 122
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.
External Links
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.