CVE-2026-6479

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-14. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 18, 2026

Advisory Details (1)

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

PostgreSQL: CVE-2026-6479: PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion

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

Patch Availability(22)

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.

Affected Packages

(14 across 9 ecosystems)
Alpine:v3.20(2)
PackageVulnerable rangeFixed inDependents
postgresql1515.18-r0
postgresql1616.14-r0
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql1616.14-r0
postgresql1717.10-r0
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql1616.14-r0
postgresql1717.10-r0
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql1717.10-r0
postgresql1818.4-r0
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql1717.10-r0
postgresql1818.4-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
postgresql-1313.10-0+deb11u1 ... 13.9-0+deb11u1 (25 versions)13.23-0+deb11u4
Debian:12(1)
PackageVulnerable rangeFixed inDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (20 versions)15.18-0+deb12u1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.5-1 ... 17.9-0+deb13u1 (6 versions)17.10-0+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (19 versions)18.4-1

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Data Freshness Timeline

(refreshed 14× in last 7d / 92× 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 262 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6479?
CVE-2026-6479 is a high vulnerability published on May 14, 2026. Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX socket to achieve sustained denial of service. If SSL and GSS are both disabled, an attacker can do the same via access to a PostgreSQL TCP socket. Versions before PostgreSQL…
When was CVE-2026-6479 disclosed?
CVE-2026-6479 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6479 actively exploited?
CVE-2026-6479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.4% of all scored CVEs.
What is the CVSS score of CVE-2026-6479?
CVE-2026-6479 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-6479?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6479, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6479

Explore →

Is Your Infrastructure Affected by CVE-2026-6479?

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