CVE-2025-8715

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2025-08-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

Improper neutralization of newlines in pg_dump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks can achieve SQL injection as a superuser of the restore target server. pg_dumpall, pg_restore, and pg_upgrade are also affected. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected. Versions before 11.20 are unaffected. CVE-2012-0868 had fixed this class of problem, but version 11.20 reintroduced it.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
30.5%
KEV
Not listed

Published

August 14, 2025

Last Modified

June 17, 2026

References (1)

Vendor Advisories for CVE-2025-8715(7)

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

Patch Availability(23)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-17 (17.6-0ubuntu0.25.04.1) @ plucky2026-05-21ubuntu
redhatpostgresql:13-8060020250825094024.ad008a3a2025-09-04redhat
redhatpostgresql:12-8020020250826135918.4cda2c842025-09-04redhat
redhatpostgresql:12-8100020250829093521.489197e62025-09-03redhat
redhatpostgresql-0:13.22-1.el9_42025-09-03redhat
redhatpostgresql:12-8040020250820054803.522a0ee42025-09-02redhat
redhatpostgresql:12-8060020250820072728.ad008a3a2025-09-02redhat
redhatpostgresql:15-8080020250815150643.63b345852025-09-02redhat
redhatpostgresql:15-8100020250818110305.489197e62025-09-02redhat
redhatpostgresql:13-8040020250818170654.522a0ee42025-09-02redhat
redhatpostgresql:12-8080020250819150429.63b345852025-09-02redhat
redhatpostgresql:13-8100020250818110147.489197e62025-09-02redhat
redhatpostgresql:15-9020020250815141744.rhel92025-09-02redhat
redhatpostgresql:13-8080020250819150623.63b345852025-09-02redhat
redhatpostgresql:15-9040020250818140154.rhel92025-09-02redhat
redhatpostgresql:16-9040020250818135852.rhel92025-09-02redhat
redhatpostgresql-0:13.22-1.el9_62025-08-28redhat
redhatpostgresql-0:13.22-1.el9_22025-08-28redhat
redhatpostgresql16-0:16.10-1.el10_02025-08-28redhat
redhatpostgresql:15-9060020250817180313.rhel92025-08-28redhat
redhatpostgresql:16-9060020250817200213.rhel92025-08-28redhat
redhatpostgresql:16-8100020250818110346.489197e62025-08-28redhat
redhatpostgresql-0:13.22-1.el9_02025-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.

Weakness Classification(1)

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

Additional Vendor Advisories

(18)

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 7× in last 7d / 43× 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.

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

Frequently asked(5)

What is CVE-2025-8715?
CVE-2025-8715 is a high vulnerability published on August 14, 2025. Improper neutralization of newlines in pgdump in PostgreSQL allows a user of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql meta-commands inside a purpose-crafted object name. The same attacks…
When was CVE-2025-8715 disclosed?
CVE-2025-8715 was first published in the National Vulnerability Database 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-8715 actively exploited?
CVE-2025-8715 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 30.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-8715?
CVE-2025-8715 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-8715?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-8715, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-8715

Explore →

Is Your Infrastructure Affected by CVE-2025-8715?

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

Start Free Scan →Browse All CVEs