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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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%
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

Published

May 14, 2026

Last Modified

May 18, 2026

Advisory Details (1)

Auto-updated May 14, 2026
Patch available.
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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.18-r0: fixed in 15.18-r0
—
postgresql16—
  • every version up to 16.14-r0: fixed in 16.14-r0
—
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.14-r0: fixed in 16.14-r0
—
postgresql17—
  • every version up to 17.10-r0: fixed in 17.10-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.14-r0: fixed in 16.14-r0
—
postgresql17—
  • every version up to 17.10-r0: fixed in 17.10-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.10-r0: fixed in 17.10-r0
—
postgresql18—
  • every version up to 18.4-r0: fixed in 18.4-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.10-r0: fixed in 17.10-r0
—
postgresql18—
  • every version up to 18.4-r0: fixed in 18.4-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1313.10-0+deb11u1 ... 13.9-0+deb11u1 (25 versions)
  • every version up to 13.23-0+deb11u4: fixed in 13.23-0+deb11u4
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (20 versions)
  • every version up to 15.18-0+deb12u1: fixed in 15.18-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1717.5-1 ... 17.9-0+deb13u1 (6 versions)
  • every version up to 17.10-0+deb13u1: fixed in 17.10-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (19 versions)
  • every version up to 18.4-1: fixed in 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 7× in last 7d / 23× 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 310 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-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?
A fix for CVE-2026-6475 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6475 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs