Skip to content
VulniPulse
High8.8Red Hat Linux

CVE-2026-116330: Red Hat Arbitrary code execution via predictable restriction key in pg_dump restore script

This Red Hat advisory covers CVE-2026-116330. Related products: Red Hat Hardened Images.

Open the Red Hat advisory

Key facts

Vendor rating
High, CVSS 8.8
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H · base score 8.8, scored by PostgreSQLAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: required. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-829 Inclusion of Functionality from Untrusted Control Sphere
EPSS
0.37% chance of exploitation in the next 30 days (31st percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Fixed in
postgresql18-main-18.7-0.1.hum1, libpq-main-18.7-0.1.hum1, postgresql17-main-17.12-0.1.hum1 and 1 more below
Source published
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Red Hat LinuxUnclassified

Description

Arbitrary code execution via predictable restriction key in pg_dump restore script. Red Hat rates this important (CVSS 8.8).

Weakness: CWE-94. Red Hat lists fixing advisory RHSA-2026:100114 with package postgresql18-main-18.7-0.1.hum1, libpq-main-18.7-0.1.hum1, postgresql17-main-17.12-0.1.hum1.

Affected product named by the advisory: Red Hat Hardened Images.

Text from the source record.

How to fix CVE-2026-116330

Upgrade to a fixed release named by Red Hat:

  • postgresql18-main-18.7-0.1.hum1
  • libpq-main-18.7-0.1.hum1
  • postgresql17-main-17.12-0.1.hum1
  • RHSA-2026:100114

Vendor guidance

  • Operational controls to mitigate this vulnerability include: 1. Avoid generating tar-format archives from untrusted database instances. By default, `pg_dump` outputs plain-text SQL. If binary or compressed archive formats are required, use the custom format (`-F c`) or directory format (`-F d`) instead of the tar format (`-F t` or `--format=tar`): pg_dump -F c -d <database_name> -f <backup_file>.dump 2. Do not execute the embedded `restore.sql` script directly using `psql`. Instead, restore custom-format archives using `pg_restore`: pg_restore -d <database_name> <backup_file>.dump 3. Restrict backup routines to verified, trusted PostgreSQL servers and ensure client commands are executed under a dedicated, unprivileged operating system service account. Caveats: Automation pipelines or scripts requiring tar-formatted archives (`-F t`) or manual execution of `restore.sql` must be adjusted to use alternative dump formats or `pg_restore`. These adjustments affect client command-line utilities and do not require restarting database services.

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Red Hat