CVE-2026-6464

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM 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 — Patch released 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.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
8.1
EG Score
8.1(medium)
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
30%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 29, 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(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-09-19ubuntu
redhatpostgresql:18-9080020260914093252.rhel92026-09-16redhat
redhatpostgresql:16-9080020260907191505.rhel92026-09-15redhat
redhatpostgresql18-0:18.6-1.el10_22026-09-14redhat

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.

Affected Packages

(11 across 7 ecosystems)
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions)15.19-0+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)17.11-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)18.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

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 37× in last 7d / 161× 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.

Showing the most recent 100 of 200 total refreshes for this CVE.

  1. 2026-09-19 16:25 UTCEG score recompute
  2. 2026-09-19 16:25 UTCVendor advisory
  3. 2026-09-19 16:25 UTCGHSA enrichment
  4. 2026-09-19 03:44 UTCEG score recompute
  5. 2026-09-19 03:44 UTCVendor advisory
  6. 2026-09-19 03:44 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 15:02 UTCVendor advisory
  9. 2026-09-18 15:01 UTCGHSA enrichment
  10. 2026-09-18 02:19 UTCEG score recompute
  11. 2026-09-18 02:19 UTCVendor advisory
  12. 2026-09-18 02:19 UTCGHSA enrichment
  13. 2026-09-17 13:37 UTCVendor advisory
  14. 2026-09-17 13:37 UTCGHSA enrichment
  15. 2026-09-17 00:11 UTCEG score recompute
  16. 2026-09-17 00:11 UTCVendor advisory
  17. 2026-09-17 00:11 UTCGHSA enrichment
  18. 2026-09-16 14:08 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-16 02:13 UTCVendor advisory
  21. 2026-09-16 02:12 UTCGHSA enrichment
  22. 2026-09-15 13:29 UTCEG score recompute
  23. 2026-09-15 13:29 UTCVendor advisory
  24. 2026-09-15 13:29 UTCGHSA enrichment
  25. 2026-09-15 03:12 UTCEPSS rescore
Show 75 more
  1. 2026-09-15 00:47 UTCVendor advisory
  2. 2026-09-15 00:47 UTCGHSA enrichment
  3. 2026-09-14 12:05 UTCVendor advisory
  4. 2026-09-14 12:05 UTCGHSA enrichment
  5. 2026-09-13 23:22 UTCEG score recompute
  6. 2026-09-13 23:22 UTCVendor advisory
  7. 2026-09-13 23:22 UTCGHSA enrichment
  8. 2026-09-13 10:41 UTCVendor advisory
  9. 2026-09-13 10:41 UTCGHSA enrichment
  10. 2026-09-12 21:59 UTCEG score recompute
  11. 2026-09-12 21:59 UTCVendor advisory
  12. 2026-09-12 21:59 UTCGHSA enrichment
  13. 2026-09-12 15:02 UTCEPSS rescore
  14. 2026-09-12 09:17 UTCVendor advisory
  15. 2026-09-12 09:17 UTCGHSA enrichment
  16. 2026-09-11 20:35 UTCEG score recompute
  17. 2026-09-11 20:35 UTCVendor advisory
  18. 2026-09-11 20:35 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-11 07:52 UTCVendor advisory
  22. 2026-09-11 07:52 UTCGHSA enrichment
  23. 2026-09-10 19:10 UTCEG score recompute
  24. 2026-09-10 19:10 UTCVendor advisory
  25. 2026-09-10 19:10 UTCGHSA enrichment
  26. 2026-09-10 06:28 UTCVendor advisory
  27. 2026-09-10 06:28 UTCGHSA enrichment
  28. 2026-09-09 17:46 UTCVendor advisory
  29. 2026-09-09 17:46 UTCGHSA enrichment
  30. 2026-09-09 05:03 UTCEG score recompute
  31. 2026-09-09 05:03 UTCVendor advisory
  32. 2026-09-09 05:03 UTCGHSA enrichment
  33. 2026-09-08 22:01 UTCEPSS rescore
  34. 2026-09-08 07:36 UTCVendor advisory
  35. 2026-09-08 07:36 UTCGHSA enrichment
  36. 2026-09-07 18:52 UTCEG score recompute
  37. 2026-09-07 18:52 UTCVendor advisory
  38. 2026-09-07 18:52 UTCGHSA enrichment
  39. 2026-09-07 16:01 UTCEPSS rescore
  40. 2026-09-07 06:09 UTCVendor advisory
  41. 2026-09-07 06:08 UTCGHSA enrichment
  42. 2026-09-06 17:27 UTCEG score recompute
  43. 2026-09-06 17:27 UTCVendor advisory
  44. 2026-09-06 17:27 UTCGHSA enrichment
  45. 2026-09-06 13:47 UTCEPSS rescore
  46. 2026-09-06 04:45 UTCVendor advisory
  47. 2026-09-06 04:45 UTCGHSA enrichment
  48. 2026-09-05 16:04 UTCEG score recompute
  49. 2026-09-05 16:04 UTCVendor advisory
  50. 2026-09-05 16:03 UTCGHSA enrichment
  51. 2026-09-05 15:31 UTCEPSS rescore
  52. 2026-09-05 03:12 UTCVendor advisory
  53. 2026-09-05 03:12 UTCGHSA enrichment
  54. 2026-09-04 14:10 UTCEG score recompute
  55. 2026-09-04 14:10 UTCVendor advisory
  56. 2026-09-04 14:09 UTCGHSA enrichment
  57. 2026-09-04 05:07 UTCEPSS rescore
  58. 2026-09-04 01:23 UTCVendor advisory
  59. 2026-09-04 01:23 UTCGHSA enrichment
  60. 2026-09-03 12:40 UTCVendor advisory
  61. 2026-09-03 12:40 UTCGHSA enrichment
  62. 2026-09-02 23:17 UTCEG score recompute
  63. 2026-09-02 23:17 UTCVendor advisory
  64. 2026-09-02 23:17 UTCGHSA enrichment
  65. 2026-09-02 14:12 UTCEPSS rescore
  66. 2026-09-02 00:29 UTCEG score recompute
  67. 2026-09-02 00:29 UTCVendor advisory
  68. 2026-09-02 00:29 UTCGHSA enrichment
  69. 2026-09-01 13:54 UTCEPSS rescore
  70. 2026-09-01 11:34 UTCEG score recompute
  71. 2026-09-01 11:34 UTCVendor advisory
  72. 2026-09-01 11:34 UTCGHSA enrichment
  73. 2026-09-01 04:40 UTCEPSS rescore
  74. 2026-08-31 21:36 UTCVendor advisory
  75. 2026-08-31 21:36 UTCGHSA enrichment

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 29, 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 70.4% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs