CVE-2020-25695

HIGHNVD 8.88.9▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.9 because EPSS predicts 46% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs). NVD baseline CVSS 8.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 46%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A 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. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

CVSS v3
8.8
EG Score
8.9HIGHhigh confidence
EG Risk
63
EG Risk 63/100CISA SSVC

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
Severity89% × 45%
Exploitation46% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
46%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: elevated) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 16, 2020

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Aug 9, 2026
Patch available. Sources: redhat.
generic

PostgreSQL: Security Information

https://www.postgresql.org/support/security/
generic

PostgreSQL: Multiple vulnerabilities (GLSA 202012-07) — Gentoo security

https://security.gentoo.org/glsa/202012-07
generic Patch Available

[SECURITY] [DLA 2478-1] postgresql-9.6 security update

https://lists.debian.org/debian-lts-announce/2020/12/msg00005.html
redhat Patch Available

1894425 – (CVE-2020-25695) CVE-2020-25695 postgresql: Multiple features escape "security restricted operation" sandbox

Affected: Red Hat Enterprise Linux 7

https://bugzilla.redhat.com/show_bug.cgi?id=1894425

Patch Availability(14)

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

(16 across 14 ecosystems)
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
postgresql15—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.18(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
postgresql15—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.10(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 9.6.0 up to 11.10-r0: fixed in 11.10-r0
—
Alpine:v3.11(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 9.6.0 up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 9.6.0 up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 9.6.0 up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.14(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 9.6.0 up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.15(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql14—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql15—
  • every version up to 12.5-r0: fixed in 12.5-r0
—
Alpine:v3.9(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql—
  • 9.6.0 up to 11.10-r0: fixed in 11.10-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-13—
  • every version up to 13.1-1: fixed in 13.1-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-9.69.6.10-0+deb9u1 ... 9.6.9-0+deb9u1 (20 versions)
  • every version up to 9.6.20-0+deb9u1: fixed in 9.6.20-0+deb9u1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

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 6× in last 7d / 25× 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 131 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2020-25695?
CVE-2020-25695 is a high vulnerability published on November 16, 2020. A 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. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser. The highest…
When was CVE-2020-25695 disclosed?
CVE-2020-25695 was first published on November 16, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-25695 actively exploited?
CVE-2020-25695 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 46% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2020-25695?
CVE-2020-25695 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9 (HIGH).
How do I remediate CVE-2020-25695?
A fix for CVE-2020-25695 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-25695 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-2020-25695

Explore →

Is Your Infrastructure Affected by CVE-2020-25695?

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