CVE-2026-6478

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-05-14. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.5Exploit: NoneExposed: 0

A fix is available — apply it.

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
6.5
EG Score
6.5(medium)
EPSS
42.5%
KEV
Not listed

Published

May 14, 2026

Last Modified

July 6, 2026

Advisory Details (1)

Auto-updated May 18, 2026
No patch confirmed yet.
generic

PostgreSQL: CVE-2026-6478: PostgreSQL discloses MD5-hashed passwords via covert timing channel

https://www.postgresql.org/support/security/CVE-2026-6478/

Vendor Advisories for CVE-2026-6478(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.4-0ubuntu0.26.04.1) @ resolute2026-06-29ubuntu
redhatpostgresql-0:13.23-1.el9_2.22026-06-25redhat
redhatpostgresql:12-8060020260623094704.ad008a3a2026-06-25redhat
redhatpostgresql-0:13.23-1.el9_4.22026-06-25redhat
redhatpostgresql-0:13.23-1.el9_6.22026-06-25redhat
redhatpostgresql:12-8100020260605152253.489197e62026-06-24redhat
redhatpostgresql:13-8100020260605152256.489197e62026-06-23redhat
redhatpostgresql:16-8100020260530205218.489197e62026-06-23redhat
redhatpostgresql:15-9080020260605124405.rhel92026-06-22redhat
redhatlibpq-0:13.23-2.el8_102026-06-22redhat
redhatpostgresql18-0:18.4-1.el10_22026-06-22redhat
redhatpostgresql16-0:16.14-1.el10_22026-06-22redhat
redhatpostgresql-0:13.23-3.el9_82026-06-22redhat
redhatpostgresql16-0:16.14-1.el10_02026-06-22redhat
redhatpostgresql:16-9060020260612084605.rhel92026-06-17redhat
redhatpostgresql:16-9040020260612132455.rhel92026-06-17redhat
redhatpostgresql:15-8080020260615085052.63b345852026-06-17redhat
redhatpostgresql:15-8100020260605152259.489197e62026-06-16redhat
redhatpostgresql:18-9080020260605125734.rhel92026-06-16redhat
redhatpostgresql:16-9080020260605131007.rhel92026-06-16redhat
redhatpostgresql18-main-18.4-0.1.hum12026-06-03redhat
redhatpostgresql17-main-17.10-0.1.hum12026-05-26redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 80× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 126 total refreshes for this CVE.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 21:56 UTCEG score recompute
  12. 2026-06-29 21:56 UTCVendor advisory
  13. 2026-06-29 21:56 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 22:51 UTCEG score recompute
  18. 2026-06-27 22:51 UTCVendor advisory
  19. 2026-06-27 22:51 UTCGHSA enrichment
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 20:24 UTCEG score recompute
  22. 2026-06-26 20:24 UTCVendor advisory
  23. 2026-06-26 20:24 UTCGHSA enrichment
  24. 2026-06-25 19:18 UTCEG score recompute
  25. 2026-06-25 19:18 UTCVendor advisory
Show 75 more
  1. 2026-06-25 19:18 UTCGHSA enrichment
  2. 2026-06-25 13:50 UTCEPSS rescore
  3. 2026-06-24 14:05 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 01:59 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-19 19:26 UTCEPSS rescore
  13. 2026-06-19 19:26 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-17 17:53 UTCEPSS rescore
  17. 2026-06-17 00:22 UTCEG score recompute
  18. 2026-06-17 00:22 UTCVendor advisory
  19. 2026-06-17 00:22 UTCGHSA enrichment
  20. 2026-06-16 17:53 UTCEPSS rescore
  21. 2026-06-16 00:05 UTCEG score recompute
  22. 2026-06-16 00:05 UTCVendor advisory
  23. 2026-06-16 00:05 UTCGHSA enrichment
  24. 2026-06-15 17:49 UTCEPSS rescore
  25. 2026-06-15 17:49 UTCEPSS rescore
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-14 08:52 UTCEG score recompute
  28. 2026-06-14 08:52 UTCVendor advisory
  29. 2026-06-14 08:52 UTCGHSA enrichment
  30. 2026-06-13 23:00 UTCEPSS rescore
  31. 2026-06-13 08:41 UTCEG score recompute
  32. 2026-06-13 08:41 UTCVendor advisory
  33. 2026-06-13 08:41 UTCGHSA enrichment
  34. 2026-06-12 23:12 UTCEPSS rescore
  35. 2026-06-12 23:12 UTCEPSS rescore
  36. 2026-06-12 08:23 UTCEG score recompute
  37. 2026-06-12 08:23 UTCVendor advisory
  38. 2026-06-12 08:22 UTCGHSA enrichment
  39. 2026-06-11 14:00 UTCEPSS rescore
  40. 2026-06-11 08:10 UTCEG score recompute
  41. 2026-06-11 08:10 UTCVendor advisory
  42. 2026-06-11 08:10 UTCGHSA enrichment
  43. 2026-06-10 22:19 UTCEPSS rescore
  44. 2026-06-10 13:22 UTCEPSS rescore
  45. 2026-06-10 07:57 UTCEG score recompute
  46. 2026-06-10 07:57 UTCVendor advisory
  47. 2026-06-10 07:57 UTCGHSA enrichment
  48. 2026-06-09 07:28 UTCEG score recompute
  49. 2026-06-09 07:28 UTCVendor advisory
  50. 2026-06-09 07:28 UTCGHSA enrichment
  51. 2026-06-08 14:17 UTCEPSS rescore
  52. 2026-06-08 07:16 UTCEG score recompute
  53. 2026-06-08 07:16 UTCVendor advisory
  54. 2026-06-08 07:16 UTCGHSA enrichment
  55. 2026-06-07 15:25 UTCEPSS rescore
  56. 2026-06-07 07:04 UTCEG score recompute
  57. 2026-06-07 07:04 UTCVendor advisory
  58. 2026-06-07 07:04 UTCGHSA enrichment
  59. 2026-06-06 13:47 UTCEPSS rescore
  60. 2026-06-06 06:52 UTCEG score recompute
  61. 2026-06-06 06:52 UTCVendor advisory
  62. 2026-06-06 06:52 UTCGHSA enrichment
  63. 2026-06-05 22:47 UTCEPSS rescore
  64. 2026-06-05 06:39 UTCEG score recompute
  65. 2026-06-05 06:39 UTCVendor advisory
  66. 2026-06-05 06:39 UTCGHSA enrichment
  67. 2026-06-05 06:10 UTCEPSS rescore
  68. 2026-06-04 13:12 UTCEPSS rescore
  69. 2026-06-04 06:27 UTCEG score recompute
  70. 2026-06-04 06:27 UTCVendor advisory
  71. 2026-06-04 06:27 UTCGHSA enrichment
  72. 2026-06-03 06:15 UTCEG score recompute
  73. 2026-06-03 06:15 UTCVendor advisory
  74. 2026-06-03 06:15 UTCGHSA enrichment
  75. 2026-06-02 20:13 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-6478?
CVE-2026-6478 is a medium vulnerability published on May 14, 2026. 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…
When was CVE-2026-6478 disclosed?
CVE-2026-6478 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6478 actively exploited?
CVE-2026-6478 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6478?
CVE-2026-6478 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-6478?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6478, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6478

Explore →

Is Your Infrastructure Affected by CVE-2026-6478?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs