PostgreSQL pg_restore_attribute_stats accepts values that cause query planning to read past end of stats array
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a PostgreSQL 18.4.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to n/a PostgreSQL 18.4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- May 14, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-126
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PostgreSQL
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postgresql | postgresql | cpe:2.3:a:postgresql:postgresql |
Using postgresql? Add it to your stack and be the first to know about CVEs like this one. (PostgreSQL)
Is PostgreSQL on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postgresql postgresql18.0 and later · before 18.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.
n/a PostgreSQL
- 18 and later · before 18.4affected · rpm
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.23 | postgresql18 | before 18.4-r0 | 18.4-r0 |
| Debian:14 | postgresql-18 | before 18.4-1 | 18.4-1 |
| openSUSE:Tumbleweed | postgresql18 | before 18.4-1.1 | 18.4-1.1 |
| Red Hat:enterprise_linux:10.2 | postgresql18 | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-contrib | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-contrib-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-debugsource | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-docs | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-docs-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-plperl | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-plperl-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-plpython3 | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-plpython3-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-pltcl-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-private-devel | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-private-libs | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-private-libs-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-server | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-server-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-server-devel | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-server-devel-debuginfo | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-static | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | postgresql18-test | before 0:18.4-1.el10_2 | 0:18.4-1.el10_2 |
+86
Same product
postgresql: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-7546PostgreSQL versions before 9.2.22, 9.3.18, 9.4.13, 9.5.8 and 9.6.4 are vulnerable to incorrect authentication flaw allowing remote attackers57Plan
- CVE-2019-9193In PostgreSQL 9.3 through 11.2, the "COPY TO/FROM PROGRAM" function allows superusers and users in the 'pg_execute_server_program' group to 55Plan
- CVE-2020-25695A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24.49Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-6478May 14, 2026 · PostgreSQL discloses MD5-hashed passwords via covert timing channel26Monitor
- ← EarlierCVE-2026-6479May 14, 2026 · PostgreSQL SSL/GSS init causes denial of service, via uncontrolled recursion30Monitor
- Later →CVE-2026-6637May 14, 2026 · PostgreSQL refint allows stack buffer overflow and SQL injection35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| n/a PostgreSQL | 18.4 | Vendor (CNA) |
| alpine:postgresql18 | 18.4-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:postgresql-18 | 18.4-1 · Debian:14 | Package registry (OSV) |
| opensuse:postgresql18 | 18.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:pg_repack | 0:1.5.3-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:pg_repack-debuginfo | 0:1.5.3-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:pg_repack-debugsource | 0:1.5.3-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:pgaudit | 0:18.0-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:pgaudit-debuginfo | 0:18.0-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:pgaudit-debugsource | 0:18.0-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:pgvector | 0:0.8.1-1.module+el9.8.0+23739+1c42644c · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:postgresql | 0:18.4-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql-test-rpm-macros | 0:18.4-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17 | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-contrib | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-docs | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-plperl | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-plpython3 | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-pltcl | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-private-devel | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-private-libs | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-server | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-server-devel | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-static | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-test | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql17-test-rpm-macros | 0:17.10-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:postgresql18 | 0:18.4-0.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:postgresql18 | 18.4-160000.1.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1467891 days apartPostgreSQL pg_trgm picksplit reads past end of buffer17Monitor
- CVE-2026-1802491 days apartPostgreSQL ascii() function reads past end of buffer17Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0254 · May 15, 2026(PostgreSQL Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-126 · Buffer Over-readCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.