CVE-2025-8714: 18.3.3
Backport ‘Bump default ruby version to 3.2.9’Backport of “Use release-environment project id instead of canonical”Backport of ‘Danger to not warn in maintained stable branches’ to 18.3Backport of “Upgrade duo workflow client protocol version”Backport of “Filter out duplicate values from the variable options dropdown”18.3: Backport of ‘Fix security widget polling indefinitely when there are sboms’[18.3 backport] Remove CVE-2025-8714 commands from structure.sqlBackport 18.3: Do not trim deployment filename in geo secondary[Backport-18.3]Wiki search throws 500 error for some wiki content[18.3] Fix search admin page error when ES server returns forbiddenBackport of “Hide secrets manager settings behind feature flag instead of just the license” to 18.3Backport of Update the admin user for GET Release Environment QA tests[18.3] Backport: Resolve “Unable to fork project or create project if application wide lockduofeaturesenabled is true”Backport of Add Danger message to guide backport MR authors to reviewers and mergers (18.3)[Backport 18-3] Skip secret push protection for as-if-foss pipeline18.3: Backport of ‘Fix error when applying scanner suggestion’Backport of Ensure proper MCP URL OAuth Discovery for API/V4/MCPOptimize HandleMalformedStrings middleware for CPU and memoryBackport to 18.3 of Add job project claims to CI ID TokensBackport of Return success when status update target already matches[18.3] Fix flaky parallel design management uploads specBackport ‘Fix branches autocomplete paths in the merge request list app’ to 18-3Backport ‘Fix Linked file not being on top of the list’ to 18-3[18.3] Allow elastic client adapter to be setBackport of Use isUnsafeLink for xcode protocol18.3 Backport of ‘Resolve “Dependency list export with API silently fails license validation”’Backport: Fix registry matadata database password creationFall back to crehash if there are multiple TLS certificates
Other sources
PostgreSQL pgdump lets superuser of origin server execute arbitrary code in psql client
— Microsoft
Untrusted data inclusion in pgdump 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. pgdumpall is also affected. pgrestore 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.
— NVD
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2025-8714?
CVE-2025-8714 has been classified with a high severity level due to its potential for arbitrary code execution.
How do I fix CVE-2025-8714?
To fix CVE-2025-8714, users should upgrade PostgreSQL to a version that is not affected, specifically versions 17.6 or later, or 16.10 or later, etc.
Who is affected by CVE-2025-8714?
CVE-2025-8714 affects PostgreSQL versions prior to 17.6, 16.10, 15.14, 14.19, and 13.22 for components like pg_dump, pg_dumpall, and pg_restore.
What impact does CVE-2025-8714 have?
The impact of CVE-2025-8714 allows a malicious superuser to execute arbitrary code on the client system during restore operations.
Is CVE-2025-8714 a remote exploit?
CVE-2025-8714 requires access to the server as a superuser, making it not a remote exploit in the typical sense.