CVE-2025-8713

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

Score 3.1 from GitHub Security Advisory (severity: LOW) published 2025-08-14. a secondary CVSS source baseline 3.1; sources differ by 0.0.

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

A fix is available — apply it.

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 v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
14
EG Risk 14/100

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
Severity31% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

Published

August 14, 2025

Last Modified

June 17, 2026

References (1)

Vendor Advisories for CVE-2025-8713(15)

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

Patch Availability(14)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupostgresql-server-dev-16 (16.10-0ubuntu0.24.04.1) @ noble2026-05-21ubuntu
redhatpostgresql:13-8060020250825094024.ad008a3a2025-09-04redhat
redhatpostgresql-0:13.22-1.el9_42025-09-03redhat
redhatpostgresql:15-8080020250815150643.63b345852025-09-02redhat
redhatpostgresql:13-8080020250819150623.63b345852025-09-02redhat
redhatpostgresql:15-9020020250815141744.rhel92025-09-02redhat
redhatpostgresql:15-9040020250818140154.rhel92025-09-02redhat
redhatpostgresql:16-9040020250818135852.rhel92025-09-02redhat
redhatpostgresql:13-8040020250818170654.522a0ee42025-09-02redhat
redhatpostgresql-0:13.22-1.el9_02025-08-28redhat
redhatpostgresql-0:13.22-1.el9_22025-08-28redhat
redhatpostgresql:16-9060020250817200213.rhel92025-08-28redhat
redhatpostgresql-0:13.22-1.el9_62025-08-28redhat
redhatpostgresql:15-9060020250817180313.rhel92025-08-28redhat

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

(13 across 9 ecosystems)
Alpine:v3.19(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.14-r0: fixed in 15.14-r0
—
postgresql16—
  • every version up to 16.10-r0: fixed in 16.10-r0
—
Alpine:v3.20(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 15.14-r0: fixed in 15.14-r0
—
postgresql16—
  • every version up to 16.10-r0: fixed in 16.10-r0
—
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.10-r0: fixed in 16.10-r0
—
postgresql17—
  • every version up to 17.6-r0: fixed in 17.6-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.10-r0: fixed in 16.10-r0
—
postgresql17—
  • every version up to 17.6-r0: fixed in 17.6-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.6-r0: fixed in 17.6-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.6-r0: fixed in 17.6-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1313.10-0+deb11u1 ... 13.9-0+deb11u1 (21 versions)
  • every version up to 13.22-0+deb11u1: fixed in 13.22-0+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (16 versions)
  • every version up to 15.14-0+deb12u1: fixed in 15.14-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1717.5-1
  • every version up to 17.6-0+deb13u1: fixed in 17.6-0+deb13u1
—

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 8× in last 7d / 23× 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 184 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-8713?
CVE-2025-8713 is a low vulnerability published on August 14, 2025. 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…
When was CVE-2025-8713 disclosed?
CVE-2025-8713 was first published on August 14, 2025, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-8713 actively exploited?
CVE-2025-8713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-8713?
CVE-2025-8713 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-8713?
A fix for CVE-2025-8713 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-8713 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-8713

Explore →

Is Your Infrastructure Affected by CVE-2025-8713?

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

Book a Demo →Browse All CVEs