CVE-2026-18408 Affecting postgresql18 package, versions <18.5-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ALPINE323-POSTGRESQL18-18833539
- published15 Aug 2026
- disclosed13 Aug 2026
Introduced: 13 Aug 2026
NewCVE-2026-18408 (opens in a new tab)How to fix?
Upgrade Alpine:3.23 postgresql18 to version 18.5-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream postgresql18 package and not the postgresql18 package as distributed by Alpine.
See How to fix? for Alpine:3.23 relevant fixed versions and status.
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.