CVE-2025-8713
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-08-14

Last updated on: 2025-08-15

Assigner: PostgreSQL

Description
PostgreSQL optimizer statistics allow a user to read sampled data within a view that the user cannot access. Separately, statistics allow a user to read sampled data that a row security policy intended to hide. PostgreSQL maintains statistics for tables by sampling data available in columns; this data is consulted during the query planning process. Prior to this release, a user could craft a leaky operator that bypassed view access control lists (ACLs) and bypassed row security policies in partitioning or table inheritance hierarchies. Reachable statistics data notably included histograms and most-common-values lists. CVE-2017-7484 and CVE-2019-10130 intended to close this class of vulnerability, but this gap remained. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-08-14
Last Modified
2025-08-15
Generated
2026-05-07
AI Q&A
2025-08-14
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 5 associated CPEs
Vendor Product Version / Range
postgresql postgresql 13.22
postgresql postgresql 16.10
postgresql postgresql 14.19
postgresql postgresql 17.6
postgresql postgresql 15.14
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1230 The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in PostgreSQL optimizer statistics allows a user to read sampled data within a view or table that they should not have access to. Specifically, users could bypass view access control lists and row security policies to access statistics data such as histograms and most-common-values lists, which are normally restricted. This happens because the statistics used for query planning can leak information despite previous fixes in earlier CVEs.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized disclosure of sensitive data by allowing users to access sampled statistical data that should be protected by access controls or row security policies. This could potentially expose information about the underlying data distribution and contents, which might be leveraged for further attacks or data inference.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, update PostgreSQL to version 17.6, 16.10, 15.14, 14.19, or 13.22 or later, as these versions contain the fix for this issue.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart