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.
CVE-2026-18408
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 29, 2026
Advisory Details (1)
Auto-updated Aug 13, 2026PostgreSQL: CVE-2026-18408: PostgreSQL psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client
https://www.postgresql.org/support/security/CVE-2026-18408/Vendor Advisories for CVE-2026-18408(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(4)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | postgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute | 2026-09-19 | ubuntu |
| redhat | postgresql:18-9080020260914093252.rhel9 | 2026-09-16 | redhat |
| redhat | postgresql:16-9080020260907191505.rhel9 | 2026-09-15 | redhat |
| redhat | postgresql18-0:18.6-1.el10_2 | 2026-09-14 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(11 across 7 ecosystems)
Alpine:v3.21(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql16 | — | 16.15-r0 | — |
| postgresql17 | — | 17.11-r0 | — |
Alpine:v3.22(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql16 | — | 16.15-r0 | — |
| postgresql17 | — | 17.11-r0 | — |
Alpine:v3.23(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql17 | — | 17.11-r0 | — |
| postgresql18 | — | 18.5-r0 | — |
Alpine:v3.24(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql17 | — | 17.11-r0 | — |
| postgresql18 | — | 18.5-r0 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql-15 | 15.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions) | 15.19-0+deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql-17 | 17.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions) | 17.11-0+deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| postgresql-18 | 18.0-1 ... 18~~devel.20250502-1 (20 versions) | 18.6-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(5)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
- Microsoft MSRCCVE-2026-184082026-08-15
PostgreSQL psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client
- Red HatRHSA-2026:67280IMPORTANT2026-08-13
RHSA-2026:67280 — Important
- Red HatRHSA-2026:67491IMPORTANT2026-08-13
RHSA-2026:67491 — Important
- Red HatRHSA-2026:67848IMPORTANT2026-08-13
RHSA-2026:67848 — Important
- UbuntuUSN-8653-1MEDIUM
PostgreSQL vulnerabilities
Data Freshness Timeline
(refreshed 40× in last 7d / 170× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 205 total refreshes for this CVE.
- 2026-09-19 12:52 UTCVendor advisory
- 2026-09-19 12:52 UTCGHSA enrichment
- 2026-09-19 00:53 UTCEG score recompute
- 2026-09-19 00:53 UTCVendor advisory
- 2026-09-19 00:52 UTCGHSA enrichment
- 2026-09-18 19:27 UTCEPSS rescore
- 2026-09-18 12:52 UTCVendor advisory
- 2026-09-18 12:52 UTCGHSA enrichment
- 2026-09-18 00:30 UTCEG score recompute
- 2026-09-18 00:30 UTCVendor advisory
- 2026-09-18 00:30 UTCGHSA enrichment
- 2026-09-17 12:14 UTCVendor advisory
- 2026-09-17 12:14 UTCGHSA enrichment
- 2026-09-17 00:11 UTCEG score recompute
- 2026-09-17 00:11 UTCVendor advisory
- 2026-09-17 00:11 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 10:48 UTCEG score recompute
- 2026-09-16 10:48 UTCVendor advisory
- 2026-09-16 10:48 UTCGHSA enrichment
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-15 21:56 UTCVendor advisory
- 2026-09-15 21:55 UTCGHSA enrichment
- 2026-09-15 08:53 UTCEG score recompute
- 2026-09-15 08:53 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-15 08:53 UTCGHSA enrichment
- 2026-09-14 20:53 UTCVendor advisory
- 2026-09-14 20:53 UTCGHSA enrichment
- 2026-09-14 05:44 UTCVendor advisory
- 2026-09-14 05:44 UTCGHSA enrichment
- 2026-09-13 17:44 UTCEG score recompute
- 2026-09-13 17:44 UTCVendor advisory
- 2026-09-13 17:44 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 05:44 UTCVendor advisory
- 2026-09-13 05:44 UTCGHSA enrichment
- 2026-09-12 17:45 UTCEG score recompute
- 2026-09-12 17:45 UTCVendor advisory
- 2026-09-12 17:45 UTCGHSA enrichment
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 05:45 UTCVendor advisory
- 2026-09-12 05:45 UTCGHSA enrichment
- 2026-09-11 17:46 UTCEG score recompute
- 2026-09-11 17:46 UTCVendor advisory
- 2026-09-11 17:46 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-11 05:46 UTCVendor advisory
- 2026-09-11 05:46 UTCGHSA enrichment
- 2026-09-10 17:46 UTCEG score recompute
- 2026-09-10 17:46 UTCVendor advisory
- 2026-09-10 17:46 UTCGHSA enrichment
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-10 05:46 UTCVendor advisory
- 2026-09-10 05:46 UTCGHSA enrichment
- 2026-09-09 17:47 UTCVendor advisory
- 2026-09-09 17:46 UTCGHSA enrichment
- 2026-09-09 05:03 UTCEG score recompute
- 2026-09-09 05:03 UTCVendor advisory
- 2026-09-09 05:03 UTCGHSA enrichment
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-08 04:37 UTCVendor advisory
- 2026-09-08 04:37 UTCGHSA enrichment
- 2026-09-07 16:37 UTCEG score recompute
- 2026-09-07 16:37 UTCVendor advisory
- 2026-09-07 16:37 UTCGHSA enrichment
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-07 01:23 UTCEG score recompute
- 2026-09-07 01:23 UTCVendor advisory
- 2026-09-07 01:23 UTCGHSA enrichment
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 13:23 UTCVendor advisory
- 2026-09-06 13:23 UTCGHSA enrichment
- 2026-09-06 01:23 UTCEG score recompute
- 2026-09-06 01:23 UTCVendor advisory
- 2026-09-06 01:23 UTCGHSA enrichment
- 2026-09-05 13:19 UTCVendor advisory
- 2026-09-05 13:19 UTCGHSA enrichment
- 2026-09-05 01:13 UTCEG score recompute
- 2026-09-05 01:13 UTCVendor advisory
- 2026-09-05 01:12 UTCGHSA enrichment
- 2026-09-04 13:11 UTCEG score recompute
- 2026-09-04 13:11 UTCVendor advisory
- 2026-09-04 13:11 UTCGHSA enrichment
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-04 01:09 UTCVendor advisory
- 2026-09-04 01:09 UTCGHSA enrichment
- 2026-09-03 12:40 UTCVendor advisory
- 2026-09-03 12:40 UTCGHSA enrichment
- 2026-09-02 23:17 UTCEG score recompute
- 2026-09-02 23:17 UTCVendor advisory
- 2026-09-02 23:17 UTCGHSA enrichment
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 23:40 UTCEG score recompute
- 2026-09-01 23:40 UTCVendor advisory
- 2026-09-01 23:40 UTCGHSA enrichment
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 11:41 UTCEG score recompute
- 2026-09-01 11:41 UTCVendor advisory
- 2026-09-01 11:41 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-18408?
When was CVE-2026-18408 disclosed?
Is CVE-2026-18408 actively exploited?
What is the CVSS score of CVE-2026-18408?
How do I remediate CVE-2026-18408?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18408
Is Your Infrastructure Affected by CVE-2026-18408?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.