CVE-2026-6478 — PostgreSQL discloses MD5-hashed passwords via covert timing channel
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.6% (30-day exploitation probability)+7
- Technical severity (medium)+3
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — www.postgresql.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Postgresql Postgresql).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Postgresql | Postgresql | < 14.23≥ 15.0 and < 15.18≥ 16.0 and < 16.14≥ 17.0 and < 17.10≥ 18.0 and < 18.4 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.2 | CVSS 3.1 | High | 3.9 | 4.2 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | 3.9 | 2.5 | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | PostgreSQL via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N (score shown at the top: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.56%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 6.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
38 on the record
- www.postgresql.org/support/security/CVE-2026-6478/
- bugzilla.redhat.com/show_bug.cgi
- access.redhat.com/errata/RHSA-2026:26525
- access.redhat.com/errata/RHSA-2026:58981
- access.redhat.com/errata/RHSA-2026:27743
- access.redhat.com/errata/RHSA-2026:27741
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-6478.json
- access.redhat.com/errata/RHSA-2026:22878
- access.redhat.com/errata/RHSA-2026:26204
- access.redhat.com/errata/RHSA-2026:34362
- access.redhat.com/errata/RHSA-2026:34043
- access.redhat.com/errata/RHSA-2026:21182
- access.redhat.com/errata/RHSA-2026:28037
- access.redhat.com/errata/RHSA-2026:27742
- access.redhat.com/errata/RHSA-2026:29212
- access.redhat.com/errata/RHSA-2026:26561
- access.redhat.com/errata/RHSA-2026:26181
- access.redhat.com/errata/RHSA-2026:29815
- access.redhat.com/security/cve/CVE-2026-6478
- access.redhat.com/errata/RHSA-2026:29904
- access.redhat.com/errata/RHSA-2026:28208
- access.redhat.com/errata/RHSA-2026:42555
- access.redhat.com/errata/RHSA-2026:28999
- access.redhat.com/errata/RHSA-2026:26203
- access.redhat.com/errata/RHSA-2026:29953
- access.redhat.com/errata/RHSA-2026:33497
- access.redhat.com/errata/RHSA-2026:26524
- access.redhat.com/errata/RHSA-2026:35880
- access.redhat.com/errata/RHSA-2026:28143
- access.redhat.com/errata/RHSA-2026:27718
- access.redhat.com/errata/RHSA-2026:49521
- access.redhat.com/errata/RHSA-2026:33441
- access.redhat.com/errata/RHSA-2026:44420
- access.redhat.com/errata/RHSA-2026:32994
- access.redhat.com/errata/RHSA-2026:34363
- access.redhat.com/errata/RHSA-2026:44481
- access.redhat.com/errata/RHSA-2026:27738
- access.redhat.com/errata/RHSA-2026:32983
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-6471 PostgreSQL logical decoding can dlopen arbitrary file Aug 13, 2026
- High CVE-2026-6464 PostgreSQL psql COPY FROM STDIN early failure processes data lines as psql commands Aug 13, 2026
- Low CVE-2026-6469 PostgreSQL ALTER TABLE ALTER TYPE resets extended statistics ownership Aug 13, 2026
- Medium CVE-2026-6470 PostgreSQL fails to check type USAGE privilege Aug 13, 2026
- High CVE-2026-19385 PostgreSQL pg_dump heap buffer overflow executes arbitrary code Aug 13, 2026
- High CVE-2026-18408 PostgreSQL psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client Aug 13, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-6478 is "PostgreSQL discloses MD5-hashed passwords via covert timing channel", rated Medium. It affects Postgresql (Postgresql); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.56% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.