CVE-2026-6464 PUBLISHED

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

Assigner: PostgreSQL
Reserved: 17.04.2026 Published: 13.08.2026 Updated: 13.08.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Score: 8.1

Product Status

Vendor n/a
Product PostgreSQL
Versions Default: unaffected
  • affected from 18 to 18.5 (excl.)
  • affected from 17 to 17.11 (excl.)
  • affected from 16 to 16.15 (excl.)
  • affected from 15 to 15.19 (excl.)
  • affected from 0 to 14.24 (excl.)

Affected Configurations

psql input uses "COPY FROM STDIN" or "\copy FROM STDIN"

Credits

  • The PostgreSQL project thanks Alexander Lakhin for reporting this problem.

References

Problem Types

  • Inclusion of Functionality from Untrusted Control Sphere CWE