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
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 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)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
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(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibpq-0:13.23-1.el8_4.12026-07-23redhat
redhatrhui5/rhua-rhel9:17847950762026-07-23redhat
redhatpostgresql:13-8080020260709122729.63b345852026-07-21redhat
redhatlibpq-0:13.23-1.el8_8.12026-07-06redhat
redhatpostgresql:13-8040020260630100922.522a0ee42026-07-01redhat
redhatpostgresql:12-8040020260624104459.522a0ee42026-07-01redhat
redhatpostgresql:12-8080020260626093604.63b345852026-07-01redhat
redhatpostgresql:15-9020020260625101129.rhel92026-06-30redhat
redhatpostgresql:15-9040020260616071806.rhel92026-06-30redhat
redhatpostgresql:15-9060020260622062902.rhel92026-06-29redhat
redhatpostgresql:13-8060020260625065744.ad008a3a2026-06-29redhat
redhatpostgresql-0:13.23-1.el9_6.22026-06-25redhat
redhatpostgresql-0:13.23-1.el9_4.22026-06-25redhat
redhatpostgresql-0:13.23-1.el9_2.22026-06-25redhat
redhatpostgresql:12-8060020260623094704.ad008a3a2026-06-25redhat
redhatpostgresql:12-8100020260605152253.489197e62026-06-24redhat
redhatpostgresql:16-8100020260530205218.489197e62026-06-23redhat
redhatpostgresql:13-8100020260605152256.489197e62026-06-23redhat
redhatpostgresql18-0:18.4-1.el10_22026-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-0:13.23-3.el9_82026-06-22redhat
redhatpostgresql:16-9040020260612132455.rhel92026-06-17redhat
redhatpostgresql:16-9060020260612084605.rhel92026-06-17redhat
redhatpostgresql:15-8080020260615085052.63b345852026-06-17redhat
redhatpostgresql:18-9080020260605125734.rhel92026-06-16redhat
redhatpostgresql:15-8100020260605152259.489197e62026-06-16redhat
redhatpostgresql:16-9080020260605131007.rhel92026-06-16redhat

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
postgresql15—15.18-r0—
postgresql16—16.14-r0—
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.14-r0—
postgresql17—17.10-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.14-r0—
postgresql17—17.10-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
postgresql18—18.4-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
postgresql18—18.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

(14)

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 75.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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