{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-18408", "assignerOrgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "state": "PUBLISHED", "assignerShortName": "PostgreSQL", "dateReserved": "2026-07-30T16:28:38.730Z", "datePublished": "2026-08-13T13:00:14.898Z", "dateUpdated": "2026-08-13T15:39:17.899Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "shortName": "PostgreSQL", "dateUpdated": "2026-08-13T13:00:14.898Z"}, "title": "PostgreSQL psql \\unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client", "x_postgresql": {"component": "client"}, "descriptions": [{"lang": "en", "value": "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."}], "affected": [{"defaultStatus": "unaffected", "product": "PostgreSQL", "vendor": "n/a", "versions": [{"lessThan": "18.5", "status": "affected", "version": "18", "versionType": "rpm"}, {"lessThan": "17.11", "status": "affected", "version": "17", "versionType": "rpm"}, {"lessThan": "16.15", "status": "affected", "version": "16", "versionType": "rpm"}, {"lessThan": "15.19", "status": "affected", "version": "15", "versionType": "rpm"}, {"lessThan": "14.24", "status": "affected", "version": "0", "versionType": "rpm"}]}], "problemTypes": [{"descriptions": [{"lang": "en", "cweId": "CWE-829", "type": "CWE", "description": "Inclusion of Functionality from Untrusted Control Sphere"}]}], "references": [{"url": "https://www.postgresql.org/support/security/CVE-2026-18408/"}], "metrics": [{"format": "CVSS", "cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "baseScore": 8.8, "baseSeverity": "HIGH"}}], "configurations": [{"lang": "en", "value": "attacker can direct pg_dump et al. to a malicious origin server"}], "workarounds": [{"lang": "en", "value": "use \"pg_restore --dbname\" instead of restore methods that involve \"psql\""}], "credits": [{"lang": "en", "value": "The PostgreSQL project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem."}]}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-08-13T13:30:14.651471Z", "id": "CVE-2026-18408", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-08-13T15:39:17.899Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-18408", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-08-13T13:30:14.651471Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-08-13T15:39:12.757Z"}}], "cna": {"title": "PostgreSQL psql \\unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client", "credits": [{"lang": "en", "value": "The PostgreSQL project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem."}], "metrics": [{"format": "CVSS", "cvssV3_1": {"version": "3.1", "baseScore": 8.8, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}}], "affected": [{"vendor": "n/a", "product": "PostgreSQL", "versions": [{"status": "affected", "version": "18", "lessThan": "18.5", "versionType": "rpm"}, {"status": "affected", "version": "17", "lessThan": "17.11", "versionType": "rpm"}, {"status": "affected", "version": "16", "lessThan": "16.15", "versionType": "rpm"}, {"status": "affected", "version": "15", "lessThan": "15.19", "versionType": "rpm"}, {"status": "affected", "version": "0", "lessThan": "14.24", "versionType": "rpm"}], "defaultStatus": "unaffected"}], "references": [{"url": "https://www.postgresql.org/support/security/CVE-2026-18408/"}], "workarounds": [{"lang": "en", "value": "use \"pg_restore --dbname\" instead of restore methods that involve \"psql\""}], "descriptions": [{"lang": "en", "value": "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."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-829", "description": "Inclusion of Functionality from Untrusted Control Sphere"}]}], "x_postgresql": {"component": "client"}, "configurations": [{"lang": "en", "value": "attacker can direct pg_dump et al. to a malicious origin server"}], "providerMetadata": {"orgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "shortName": "PostgreSQL", "dateUpdated": "2026-08-13T13:00:14.898Z"}}}, "cveMetadata": {"cveId": "CVE-2026-18408", "state": "PUBLISHED", "dateUpdated": "2026-08-13T15:39:17.899Z", "dateReserved": "2026-07-30T16:28:38.730Z", "assignerOrgId": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "datePublished": "2026-08-13T13:00:14.898Z", "assignerShortName": "PostgreSQL"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "PostgreSQL", "vendor": "n/a", "versions": [{"lessThan": "18.5", "status": "affected", "version": "18", "versionType": "rpm"}, {"lessThan": "17.11", "status": "affected", "version": "17", "versionType": "rpm"}, {"lessThan": "16.15", "status": "affected", "version": "16", "versionType": "rpm"}, {"lessThan": "15.19", "status": "affected", "version": "15", "versionType": "rpm"}, {"lessThan": "14.24", "status": "affected", "version": "0", "versionType": "rpm"}]}], "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "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."}], "id": "CVE-2026-18408", "lastModified": "2026-08-13T16:17:58.420", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 8.8, "baseSeverity": "HIGH", "confidentialityImpact": "HIGH", "integrityImpact": "HIGH", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "REQUIRED", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 5.9, "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-18408", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-08-13T13:30:14.651471Z", "version": "2.0.3"}}]}, "published": "2026-08-13T13:17:48.127", "references": [{"source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "url": "https://www.postgresql.org/support/security/CVE-2026-18408/"}], "sourceIdentifier": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-829"}], "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[18,18.5)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[17,17.11)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[16,16.15)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[15,15.19)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[0,14.24)"}}], "enrichment": {"confidence": 90.0, "confidence_source": "inferred", "scores": [{"score": 90.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "PostgreSQL", "source": "cna", "vendor": "n/a"}, "product": "postgresql", "vendor": "postgresql"}], "created": "2026-08-13T14:45:03.242866+00:00", "updated": "2026-08-13T15:00:04.004504+00:00", "vendors": ["postgresql", "postgresql$PRODUCT$postgresql"]}