PoC Monitor
← All CVEs
CVE-2025-8714published 14 Aug 2025 13:00 UTCData: JSON · API

PostgreSQL

PostgreSQL pg_dump lets superuser of origin server execute arbitrary code in psql client

Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser 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. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. This is similar to MySQL CVE-2024-21096. Versions before PostgreSQL 17.6, 16.10, 15.14, 14.19, and 13.22 are affected.

First public PoC 17 daysafter publication · 31 Aug 2025
Public PoCs11 on GitHub
CVSS8.8high · scored by CNA · CWE-829
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

n/a PostgreSQL
  • >= 17, < 17.6
  • >= 16, < 16.10
  • >= 15, < 15.14
  • >= 14, < 14.19
  • < 13.22

Fixed in 17.6, 16.10, 15.14, 14.19, 13.22

Mitigation

Upgrade PostgreSQL to 17.6 or 16.10 or 15.14 or 14.19 or 13.22 or later.

Workaround

use "pg_restore --dbname" instead of restore methods that involve "psql"

Timeline

Days relative to CVE publication
-3t=0+3+6+9+12+15+18CVE published14 Aug 2025 · t = 0First public PoC31 Aug 2025 · t+17d

First public PoC 17 days after publication; not in CISA KEV. First PoC: orderby99/CVE-2025-8714-POC (created 31 Aug 2025, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
orderby99/CVE-2025-8714-POC 31 Aug 2025 +17 d 2 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.