CVE-2026-6475

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin superuser, due to features like shared_preload_libraries. Hence, the attack has practical implications only if one takes relevant action between these commands and server start, like moving the files to a different VM or snapshotting the VM. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
24.3%
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-6475: PostgreSQL pg_basebackup and pg_rewind can overwrite unrelated files of origin superuser choice

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

Vendor Advisories for CVE-2026-6475(20)

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

Patch Availability(19)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-14 (14.23-0ubuntu0.22.04.1) @ jammy2026-06-29ubuntu
redhatpostgresql-0:13.23-1.el9_6.22026-06-25redhat
redhatpostgresql:12-8060020260623094704.ad008a3a2026-06-25redhat
redhatpostgresql-0:13.23-1.el9_2.22026-06-25redhat
redhatpostgresql-0:13.23-1.el9_4.22026-06-25redhat
redhatpostgresql18-0:18.4-1.el10_22026-06-22redhat
redhatpostgresql-0:13.23-3.el9_82026-06-22redhat
redhatlibpq-0:13.23-2.el8_102026-06-22redhat
redhatpostgresql:15-9080020260605124405.rhel92026-06-22redhat
redhatpostgresql16-0:16.14-1.el10_22026-06-22redhat
redhatpostgresql16-0:16.14-1.el10_02026-06-22redhat
redhatpostgresql:15-8080020260615085052.63b345852026-06-17redhat
redhatpostgresql:16-9060020260612084605.rhel92026-06-17redhat
redhatpostgresql:16-9040020260612132455.rhel92026-06-17redhat
redhatpostgresql:15-8100020260605152259.489197e62026-06-16redhat
redhatpostgresql:16-9080020260605131007.rhel92026-06-16redhat
redhatpostgresql:18-9080020260605125734.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

(7)

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

Frequently asked(5)

What is CVE-2026-6475?
CVE-2026-6475 is a high vulnerability published on May 14, 2026. Symlink following in PostgreSQL pgbasebackup plain format and in pgrewind allows an origin superuser to overwrite local files, e.g. /var/lib/postgres/.bashrc, that hijack the operating system account. It will remain the case that starting the server after these commands implicitly trusts the origin…
When was CVE-2026-6475 disclosed?
CVE-2026-6475 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-6475 actively exploited?
CVE-2026-6475 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6475?
CVE-2026-6475 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-6475?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6475, 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-6475

Explore →

Is Your Infrastructure Affected by CVE-2026-6475?

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

Start Free Scan →Browse All CVEs