Skip to content
VulniPulse
Critical 2 vendors · 2 advisories

CVE-2026-18408: PostgreSQL psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client

CVE-2026-18408 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
Critical
CVSS base score
8.4 (Red Hat)
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.36% chance of exploitation in the next 30 days (29th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
Fixed releases
  • Red Hat: postgresql18-0:18.6-1.el10_2, postgresql16-0:16.15-1.el10_2, postgresql16-0:16.15-1.el10_0, postgresql-0:9.2.24-9.el7_9.7, postgresql:16-8100020260910192321.489197e6, postgresql:15-8100020260906175012.489197e6 and 38 more in the advisory
Vendor advisories
2 from Red Hat, Splunk
Assigned by
PostgreSQL (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-18408; each belongs to its advisory, not to every product listed. How records are collected and checked.

Description

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 \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

Text from the CVE.org record (PostgreSQL).

How do I fix CVE-2026-18408?

Upgrade to a fixed release named by the vendor:

  • Red Hat: postgresql18-0:18.6-1.el10_2, postgresql16-0:16.15-1.el10_2, postgresql16-0:16.15-1.el10_0, postgresql-0:9.2.24-9.el7_9.7, postgresql:16-8100020260910192321.489197e6, postgresql:15-8100020260906175012.489197e6
  • To mitigate this vulnerability, administrators should avoid generating or restoring pg_dump files from untrusted or public origin servers using the psql client. If restoring a plain-format dump from an unverified source is strictly necessary, manually inspect the file for unauthorized \restrict or \unrestrict meta-commands before execution, or isolate the restore process in a sandboxed environment (Red Hat)
  • Workaround: use "pg_restore --dbname" instead of restore methods that involve "psql" (CVE.org record)

Vendor advisories for CVE-2026-18408

Red Hat

1 advisory
  • Advisory severityHigh8.4

    High [CVE-2026-18408] Arbitrary code execution via untrusted data inclusion in pg_dump

    CVE-2026-18408Source published Source updated

    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 \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected. An Important-rated vulnerability in PostgreSQL allows a malicious superuser on an origin server to compromise client systems…

    Affected products in this advisory
    • Red Hat Enterprise Linux 10.0 Extended Update Support
    • Red Hat Enterprise Linux 7 Extended Lifecycle Support
    • Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support
    • Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On

    12 more entries in the full advisory.

    Source-reported affected versions
    • < 18.5
    • < 17.11
    • < 16.15
    • < 15.19

    1 more entries in the full advisory.

    Source-reported fixed versions
    • postgresql18-0:18.6-1.el10_2
    • postgresql16-0:16.15-1.el10_2
    • postgresql16-0:16.15-1.el10_0
    • postgresql-0:9.2.24-9.el7_9.7

    40 more entries in the full advisory.

    Mitigation guidance
    • To mitigate this vulnerability, administrators should avoid generating or restoring pg_dump files from untrusted or public origin servers using the psql client. If restoring a plain-format dump from an unverified source is strictly necessary, manually inspect the file for unauthorized \restrict or \unrestrict meta-commands before execution, or isolate the restore process in a sandboxed environment

Splunk

1 advisory
  • Advisory severityCritical

    Critical [CVE-2025-61726 +79] Third-Party Package Updates in Splunk Enterprise - November 2026

    SVD-2026-1104Source published

    This bulletin covers 80 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.

    Splunk remedied common vulnerabilities and exposures (CVEs) in third-party packages in Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher. Affected products named by the advisory: Splunk Enterprise 10.6; Splunk Enterprise 10.4; Splunk Enterprise 10.2; Splunk Enterprise 10.0; and 1 more. Affected products named by the advisory: Splunk Enterprise 9.4.

    Affected products in this advisory
    • Splunk Enterprise 10.6
    • Splunk Enterprise 10.4
    • Splunk Enterprise 10.2
    • Splunk Enterprise 10.0

    1 more entries in the full advisory.

    Source-reported affected versions
    • Splunk Enterprise 10.6.0.5
    • Splunk Enterprise 10.4.0 to 10.4.4
    • Splunk Enterprise 10.2.0 to 10.2.8
    • Splunk Enterprise 10.0.0 to 10.0.11

    1 more entries in the full advisory.

    Source-reported fixed versions
    • Splunk Enterprise 10.6.1
    • Splunk Enterprise 10.4.5
    • Splunk Enterprise 10.2.9
    • Splunk Enterprise 10.0.12

    1 more entries in the full advisory.

    Mitigation guidance
    • Upgrade Splunk Enterprise to an applicable fixed release identified in the OSS entries below. The listed versions contain different component updates; the details specify which releases contain each fix.

References

Timeline

  1. CVE record published
  2. CVE record last updated
  3. First vendor advisory listed by VulniPulse

All Red Hat 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