CVE-2026-6464

PostgreSQL psql COPY FROM STDIN early failure processes data lines as psql commands

HIGH
8.1
CVSS Score
Published: August 13, 2026 at 01:00 PM UTC
Updated: August 29, 2026 at 11:33 PM UTC
1 product affected across 1 vendorPostgreSQL

Using PostgreSQL by N/A?

Get instant alerts when new vulnerabilities affect PostgreSQL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 14.2414.0 ≤ v < 14.2415 ≤ v < 15.1915.0 ≤ v < 15.1916 ≤ v < 16.1516.0 ≤ v < 16.1517 ≤ v < 17.1117.0 ≤ v < 17.1118 ≤ v < 18.618.0 ≤ v < 18.515161718
Affected range stops below 14.24, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.15, so it looks safe — our inference, not a vendor statement
Affected range stops below 17.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 18.6, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHPostgreSQL
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-829

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card