CVE-2026-18408

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(high)
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 computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

PostgreSQL: 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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-08-21ubuntu

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

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.

Data Freshness Timeline

(refreshed 30× in last 7d / 41× 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.

  1. 2026-08-21 03:07 UTCEG score recompute
  2. 2026-08-21 03:07 UTCVendor advisory
  3. 2026-08-21 03:07 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 15:08 UTCVendor advisory
  6. 2026-08-20 15:08 UTCGHSA enrichment
  7. 2026-08-20 03:03 UTCEG score recompute
  8. 2026-08-20 03:03 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 15:04 UTCGHSA enrichment
  11. 2026-08-19 03:30 UTCGHSA enrichment
  12. 2026-08-18 15:30 UTCEG score recompute
  13. 2026-08-18 15:29 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-18 05:29 UTCGHSA enrichment
  16. 2026-08-17 17:29 UTCEG score recompute
  17. 2026-08-17 17:29 UTCGHSA enrichment
  18. 2026-08-17 13:47 UTCEPSS rescore
  19. 2026-08-17 05:24 UTCGHSA enrichment
  20. 2026-08-16 17:21 UTCEG score recompute
  21. 2026-08-16 17:21 UTCGHSA enrichment
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 05:22 UTCEG score recompute
  24. 2026-08-16 05:22 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 16 more
  1. 2026-08-15 17:23 UTCGHSA enrichment
  2. 2026-08-15 05:24 UTCEG score recompute
  3. 2026-08-15 05:24 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 17:24 UTCGHSA enrichment
  6. 2026-08-14 05:25 UTCEG score recompute
  7. 2026-08-14 05:25 UTCGHSA enrichment
  8. 2026-08-14 04:24 UTCEG score recompute
  9. 2026-08-14 04:24 UTCGHSA enrichment
  10. 2026-08-13 16:29 UTCEG score recompute
  11. 2026-08-13 16:29 UTCGHSA enrichment
  12. 2026-08-13 16:01 UTCEG score recompute
  13. 2026-08-13 16:01 UTCGHSA enrichment
  14. 2026-08-13 13:35 UTCEG score recompute
  15. 2026-08-13 13:17 UTCEG score recompute
  16. 2026-08-13 13:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18408?
CVE-2026-18408 is a high vulnerability published on August 13, 2026. Untrusted data inclusion in pgdump 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…
When was CVE-2026-18408 disclosed?
CVE-2026-18408 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18408 actively exploited?
CVE-2026-18408 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 57.6% of all scored CVEs.
What is the CVSS score of CVE-2026-18408?
CVE-2026-18408 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-18408?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18408, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18408

Explore →

Is Your Infrastructure Affected by CVE-2026-18408?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs