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

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.

Published: 2026-05-14 Last update: 2026-05-18 Assigner: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 Source: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-6575 is rated Low Risk (20/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.03%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-6575

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-15 — 0.03% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-6575

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 f86ef6dc-4d3a-42ad-8f28-e6d5547a5007

Weakness enumeration for CVE-2026-6575

GitHub Security Advisory for CVE-2026-6575

GHSA-f8xc-gmqx-v9fh · Severity: medium — Buffer over-read in PostgreSQL function pg_restore_attribute_stats() accepts array values of...

OS Trackers for CVE-2026-6575

vendor priority summary link
debian not yet assigned CVE-2026-6575 not yet assigned priority: Debian including 1 source packages (postgresql-18), 2 status rows across 2 suites (forky, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-6575
suse medium CVE-2026-6575 severity moderate: SUSE including 82 source package names (libecpg6, libecpg6-18.4-150200.5.12.1, …), 668 product×package rows across 29 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS, SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, … (29 product lines)): Known Not Affected 585, Fixed 83. https://www.suse.com/security/cve/CVE-2026-6575/
ubuntu medium CVE-2026-6575 medium priority: Ubuntu including 8 source packages (postgresql-10, postgresql-12, …), 44 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 28, needs-triage 7, ignored 4, released 4, deferred 1. https://ubuntu.com/security/CVE-2026-6575

Affected software / configurations for CVE-2026-6575

Vendor Product Version Raw CPE
postgresql postgresql >= 18.0, < 18.4 cpe:2.3:a:postgresql:postgresql:*:*:*:*:*:*:*:*

References for CVE-2026-6575

cvelogic Threat Intelligence