CVE-2026-6575

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

Buffer over-read in PostgreSQL function pg_restore_attribute_stats() accepts array values of unmatched length, which causes query planning to read past end of one array. This allows a table maintainer to infer memory values past that array end. Within major version 18, minor versions before PostgreSQL 18.4 are affected. Versions before PostgreSQL 18 are unaffected.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 18, 2026

Advisory Details (1)

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

PostgreSQL: CVE-2026-6575: PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array

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

Vendor Advisories for CVE-2026-6575(4)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-14 (14.23-0ubuntu0.22.04.1) @ jammy2026-08-23ubuntu
redhatpostgresql18-0:18.4-1.el10_22026-06-22redhat
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.

Affected Packages

(3 across 3 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
postgresql18—18.4-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
postgresql18—18.4-r0—
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

(1)

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 4× in last 7d / 37× 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 240 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6575?
CVE-2026-6575 is a medium vulnerability published on May 14, 2026. Buffer over-read in PostgreSQL function pgrestoreattribute_stats() accepts array values of unmatched length, which causes query planning to read past end of one array. This allows a table maintainer to infer memory values past that array end. Within major version 18, minor versions before…
When was CVE-2026-6575 disclosed?
CVE-2026-6575 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-6575 actively exploited?
CVE-2026-6575 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 89.0% of all scored CVEs.
What is the CVSS score of CVE-2026-6575?
CVE-2026-6575 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-6575?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6575, 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-6575

Explore →

Is Your Infrastructure Affected by CVE-2026-6575?

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

Start Free Scan →Browse All CVEs