Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
use pg_restore instead of running restore.sql
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 13 Nov 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-94 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Thu, 12 Nov 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql postgresql |
|
| Vendors & Products |
Postgresql
Postgresql postgresql |
Thu, 12 Nov 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Untrusted data inclusion in PostgreSQL pg_dump tar-format restore.sql allows a compromised origin server to execute arbitrary code as the client operating system account running psql, via the predictable restriction key in restore.sql. This is a gap in the fix for CVE-2025-8714. restore.sql is undocumented. Versions before PostgreSQL 18.7, 17.12, 16.16, 15.20, and 14.25 are affected. | |
| Title | PostgreSQL pg_dump tar restore.sql fails to block psql command injection | |
| Weaknesses | CWE-829 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-11-12T14:15:17.385Z
Reserved: 2026-10-26T03:52:44.054Z
Link: CVE-2026-116330
No data.
Status : Awaiting Analysis
Published: 2026-11-12T15:17:41.557
Modified: 2026-11-12T19:02:35.830
Link: CVE-2026-116330
OpenCVE Enrichment
Updated: 2026-11-12T23:30:10Z