PostgreSQL up to 18.3 pg_restore_attribute_stats buffer over-read
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in PostgreSQL up to 18.3 and classified as problematic. This affects the function pg_restore_attribute_stats. This manipulation causes buffer over-read.
This vulnerability is tracked as CVE-2026-6575. The attack is possible to be carried out remotely. No exploit exists.
The affected component should be upgraded.
Details
A vulnerability was found in PostgreSQL up to 18.3. It has been declared as problematic. Affected by this vulnerability is the function pg_restore_attribute_stats. The manipulation with an unknown input leads to a buffer over-read vulnerability. The CWE definition for the vulnerability is CWE-126. The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The advisory is shared at postgresql.org. This vulnerability is known as CVE-2026-6575 since 04/19/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 315292 (SUSE SLES12 Security Update : postgresql18 (SUSE-SU-2026:1946-1)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 18.4 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (315292) and CERT Bund (WID-SEC-2026-1544). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- RESF Rocky Linux
- Open Source PostgreSQL
- IBM QRadar SIEM
Product
Type
Name
Version
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (PostgreSQL): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Buffer over-readCWE: CWE-126 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 315292
Nessus Name: SUSE SLES12 Security Update : postgresql18 (SUSE-SU-2026:1946-1)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: PostgreSQL 18.4
Timeline
04/19/2026 CVE reserved05/14/2026 Advisory disclosed
05/14/2026 VulDB entry created
06/25/2026 VulDB entry last update
Sources
Product: postgresql.orgAdvisory: postgresql.org
Status: Confirmed
CVE: CVE-2026-6575 (🔒)
GCVE (CVE): GCVE-0-2026-6575
GCVE (VulDB): GCVE-100-363877
CERT Bund: WID-SEC-2026-1544 - PostgreSQL: Mehrere Schwachstellen
Entry
Created: 05/14/2026 15:50Updated: 06/25/2026 20:07
Changes: 05/14/2026 15:50 (63), 05/16/2026 00:14 (7), 05/19/2026 17:38 (2), 05/28/2026 10:16 (1), 06/15/2026 15:33 (1), 06/25/2026 20:07 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.