Untrusted data inclusion in PostgreSQL psql COPY may allow a server administrator to elicit execution of data lines as psql commands, via error injection. If the "COPY FROM STDIN" or "\copy FROM STDIN" command fails before the server indicates that it awaits input rows, psql processes the in-line data rows as psql commands. "COPY FROM" with a filename is unaffected. The server administrator has no inherent control over the data rows, so a complete attack requires the attacker to separately acquire control of both the server and the data rows. Alternatively, an attacker controlling data rows alone might complete an attack through a coincidental error that they don't control. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-6464
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 19, 2026
Advisory Details (1)
Auto-updated Aug 13, 2026PostgreSQL: CVE-2026-6464: PostgreSQL psql COPY FROM STDIN early failure processes data lines as psql commands
https://www.postgresql.org/support/security/CVE-2026-6464/Vendor Advisories for CVE-2026-6464(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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | postgresql-server-dev-16 (16.15-0ubuntu0.24.04.1) @ noble | 2026-08-20 | ubuntu |
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 31× in last 7d / 40× 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.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 16:48 UTCVendor advisory
- 2026-08-20 16:48 UTCGHSA enrichment
- 2026-08-20 03:48 UTCEG score recompute
- 2026-08-20 03:48 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:04 UTCGHSA enrichment
- 2026-08-19 04:13 UTCGHSA enrichment
- 2026-08-18 15:29 UTCEG score recompute
- 2026-08-18 15:29 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 10:59 UTCGHSA enrichment
- 2026-08-17 22:17 UTCEG score recompute
- 2026-08-17 22:17 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 09:35 UTCGHSA enrichment
- 2026-08-16 20:54 UTCEG score recompute
- 2026-08-16 20:54 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:12 UTCEG score recompute
- 2026-08-16 08:12 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 19:31 UTCGHSA enrichment
Show 15 moreShow fewer
- 2026-08-15 06:49 UTCEG score recompute
- 2026-08-15 06:49 UTCGHSA enrichment
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 18:06 UTCGHSA enrichment
- 2026-08-14 05:25 UTCEG score recompute
- 2026-08-14 05:25 UTCGHSA enrichment
- 2026-08-14 04:24 UTCEG score recompute
- 2026-08-14 04:24 UTCGHSA enrichment
- 2026-08-13 16:29 UTCEG score recompute
- 2026-08-13 16:29 UTCGHSA enrichment
- 2026-08-13 16:01 UTCEG score recompute
- 2026-08-13 16:01 UTCGHSA enrichment
- 2026-08-13 13:35 UTCEG score recompute
- 2026-08-13 13:17 UTCEG score recompute
- 2026-08-13 13:16 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p97HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p95HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-829
- CVE-2021-41037EG 10.0CRITICAL
- CVE-2022-1161EG 10.0EPSS p92CRITICAL
- CVE-2020-4561EG 10.0CRITICAL
- CVE-2022-24119EG 9.8CRITICAL
- CVE-2020-16152EG 9.8EPSS p98CRITICAL
- CVE-2021-21804EG 9.8CRITICAL
- CVE-2020-25414EG 9.8CRITICAL
- CVE-2020-3794EG 9.8EPSS p94CRITICAL
- CVE-2020-8128EG 9.8CRITICAL
- CVE-2012-4919EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-6464?
When was CVE-2026-6464 disclosed?
Is CVE-2026-6464 actively exploited?
What is the CVSS score of CVE-2026-6464?
How do I remediate CVE-2026-6464?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6464
Is Your Infrastructure Affected by CVE-2026-6464?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.