Skip to content
major vulnerability· requires attention

PostgreSQL is widely deployed; psql client command-injection can affect DB admins and automation across industries, posing broad operational risk.

Applications

CVE-2026-6464

8.1
High
EPSS 0.36%Patch availableAug 13, 2026

psql COPY FROM STDIN can treat data rows as commands, enabling command injection.

common questions

Is CVE-2026-6464 being exploited?

Not confirmed. CVE-2026-6464 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.36% probability of exploitation in the next 30 days.

How severe is CVE-2026-6464?

CVE-2026-6464 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-6464?

Yes. A fix has been recorded for CVE-2026-6464. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-6464 affect?

CVE-2026-6464 affects psql client, PostgreSQL < 18.5, 17.11, 16.15, 15.19, 14.24, apps using COPY FROM STDIN or \copy FROM STDIN. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-6464?

Upgrade PostgreSQL/psql to fixed versions and avoid COPY FROM STDIN from untrusted sources.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
psql clientPostgreSQL < 18.5, 17.11, 16.15, 15.19, 14.24apps using COPY FROM STDIN or \copy FROM STDIN
impact

Attacker-controlled data or a compromised server can cause psql to execute data rows as psql commands, enabling command injection, unauthorized DB/client actions, and potential admin-level abuse.

action required

Patch when possible

affected versions
PostgreSQL
  • affected>= 18 and < 18.6
  • affected>= 17 and < 17.11
  • affected>= 16 and < 16.15
  • affected>= 15 and < 15.19
  • affected< 14.24

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free