Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-8715PostgreSQL pg_dump newline in object name executes arbitrary code in psql client and in restore target server

Description

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.

Timeline

  1. ID reserved

    By PostgreSQL

  2. · 7 days later

    Published

  3. · 7 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-8715, by who scored it
Scored byCVSSScoreVector
PostgreSQLCNA (assigner)3.1High8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.47% · top 58% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • PostgreSQL

    • affected 17 – < 17.6
    • affected 16 – < 16.10
    • affected 15 – < 15.14
    • affected 14 – < 14.19
    • affected 11.20 – < 13.22

What to do

Workaround: To block attacks against the psql client, use "pg_restore --dbname" instead of restore methods that involve "psql". To block SQL injection against the restore target server, revoke the CREATE permission from non-superusers at the origin server.

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-8715 badge
[![CVE-2025-8715](https://cveledger.app/badge/CVE-2025-8715.svg)](https://cveledger.app/cve/CVE-2025-8715)

Record last updated .