Skip to main content
VulnerabilityPublished Updated

CVE-2026-18408: PostgreSQL · Untrusted Functionality Inclusion

Affects PostgreSQLSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 8.8 High · fixed in 18.6 : patch PostgreSQL soon.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 18.6, 17.11, 16.15 +3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
PostgreSQLAffected
  • >=18 <18.6
Fixed in
  • 18.6
PostgreSQLAffected
  • >=17 <17.11
Fixed in
  • 17.11
PostgreSQLAffected
  • >=16 <16.15
Fixed in
  • 16.15
PostgreSQLAffected
  • >=15 <15.19
Fixed in
  • 15.19
PostgreSQLAffected
  • <14.24
Fixed in
  • 14.24
Postgresqlpostgresql/postgresqlpkg:deb/postgresql/postgresqlOther threatsAffected
  • <14.24
  • <15.19
  • <16.15
  • <17.11
  • <18.5
Fixed in
  • 14.24
  • 15.19
  • 16.15
  • 17.11
  • 18.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The vulnerability description notes that fixes were introduced in PostgreSQL versions 14.24, 15.19, 16.15, 17.11, and 18.5. Users should upgrade to these or later versions to mitigate the vulnerability. Until patched, avoid restoring dumps from untrusted sources and restrict superuser access on origin servers.

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.

References

Community reviews

Loading reviews…