CVE-2026-6464

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

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 computed
Severity81% × 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, 2026
No patch confirmed yet.
generic

PostgreSQL: 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 / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-16 (16.15-0ubuntu0.24.04.1) @ noble2026-08-20ubuntu

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.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 16:48 UTCVendor advisory
  3. 2026-08-20 16:48 UTCGHSA enrichment
  4. 2026-08-20 03:48 UTCEG score recompute
  5. 2026-08-20 03:48 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 15:04 UTCGHSA enrichment
  8. 2026-08-19 04:13 UTCGHSA enrichment
  9. 2026-08-18 15:29 UTCEG score recompute
  10. 2026-08-18 15:29 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 10:59 UTCGHSA enrichment
  14. 2026-08-17 22:17 UTCEG score recompute
  15. 2026-08-17 22:17 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 09:35 UTCGHSA enrichment
  18. 2026-08-16 20:54 UTCEG score recompute
  19. 2026-08-16 20:54 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 08:12 UTCEG score recompute
  23. 2026-08-16 08:12 UTCGHSA enrichment
  24. 2026-08-16 02:15 UTCEPSS rescore
  25. 2026-08-15 19:31 UTCGHSA enrichment
Show 15 more
  1. 2026-08-15 06:49 UTCEG score recompute
  2. 2026-08-15 06:49 UTCGHSA enrichment
  3. 2026-08-15 01:31 UTCEPSS rescore
  4. 2026-08-14 18:06 UTCGHSA enrichment
  5. 2026-08-14 05:25 UTCEG score recompute
  6. 2026-08-14 05:25 UTCGHSA enrichment
  7. 2026-08-14 04:24 UTCEG score recompute
  8. 2026-08-14 04:24 UTCGHSA enrichment
  9. 2026-08-13 16:29 UTCEG score recompute
  10. 2026-08-13 16:29 UTCGHSA enrichment
  11. 2026-08-13 16:01 UTCEG score recompute
  12. 2026-08-13 16:01 UTCGHSA enrichment
  13. 2026-08-13 13:35 UTCEG score recompute
  14. 2026-08-13 13:17 UTCEG score recompute
  15. 2026-08-13 13:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-6464?
CVE-2026-6464 is a high vulnerability published on August 13, 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…
When was CVE-2026-6464 disclosed?
CVE-2026-6464 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6464 actively exploited?
CVE-2026-6464 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 59.7% of all scored CVEs.
What is the CVSS score of CVE-2026-6464?
CVE-2026-6464 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-6464?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6464, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6464

Explore →

Is Your Infrastructure Affected by CVE-2026-6464?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.