PostgreSQL 6.x — End of Life
EOL High riskPostgreSQL 6.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 6.5 | Jun 9, 1999 | — | Jun 9, 2004 | 6.5.3 | EOL |
| 6.4 | Oct 30, 1998 | — | Oct 30, 2003 | 6.4.2 | EOL |
| 6.3 | Mar 1, 1998 | — | Mar 1, 2003 | 6.3.2 | EOL |
CVEs affecting PostgreSQL 6.x (24)
| CVE | Severity | CVSS | EPSS | KEV | Cycle | Description | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-6637 | HIGH | 8.8 | 0.04% | — | 6.4 | Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as th… | May 14, 2026 |
| CVE-2026-6473 | HIGH | 8.8 | 0.07% | — | 6.3 | Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to un… | May 14, 2026 |
| CVE-2026-6473 | HIGH | 8.8 | 0.07% | — | 6.5 | Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to un… | May 14, 2026 |
| CVE-2026-6473 | HIGH | 8.8 | 0.07% | — | 6.4 | Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to un… | May 14, 2026 |
| CVE-2026-6475 | HIGH | 8.8 | 0.05% | — | 6.3 | Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite loca… | May 14, 2026 |
| CVE-2026-6475 | HIGH | 8.8 | 0.05% | — | 6.5 | Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite loca… | May 14, 2026 |
| CVE-2026-6475 | HIGH | 8.8 | 0.05% | — | 6.4 | Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite loca… | May 14, 2026 |
| CVE-2026-6477 | HIGH | 8.8 | 0.05% | — | 6.3 | Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lsee… | May 14, 2026 |
| CVE-2026-6477 | HIGH | 8.8 | 0.05% | — | 6.5 | Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lsee… | May 14, 2026 |
| CVE-2026-6477 | HIGH | 8.8 | 0.05% | — | 6.4 | Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lsee… | May 14, 2026 |
| CVE-2026-6637 | HIGH | 8.8 | 0.04% | — | 6.3 | Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as th… | May 14, 2026 |
| CVE-2026-6637 | HIGH | 8.8 | 0.04% | — | 6.5 | Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as th… | May 14, 2026 |
| CVE-2026-6479 | HIGH | 7.5 | 0.02% | — | 6.5 | Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX … | May 14, 2026 |
| CVE-2026-6479 | HIGH | 7.5 | 0.02% | — | 6.4 | Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX … | May 14, 2026 |
| CVE-2026-6479 | HIGH | 7.5 | 0.02% | — | 6.3 | Uncontrolled recursion in PostgreSQL SSL and GSS negotiation allows an attacker able to connect to a PostgreSQL AF_UNIX … | May 14, 2026 |
| CVE-2026-6478 | MEDIUM | 6.5 | 0.08% | — | 6.4 | Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover us… | May 14, 2026 |
| CVE-2026-6478 | MEDIUM | 6.5 | 0.08% | — | 6.5 | Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover us… | May 14, 2026 |
| CVE-2026-6478 | MEDIUM | 6.5 | 0.08% | — | 6.3 | Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover us… | May 14, 2026 |
| CVE-2026-6472 | MEDIUM | 5.4 | 0.03% | — | 6.4 | Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to… | May 14, 2026 |
| CVE-2026-6472 | MEDIUM | 5.4 | 0.03% | — | 6.3 | Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to… | May 14, 2026 |
| CVE-2026-6472 | MEDIUM | 5.4 | 0.03% | — | 6.5 | Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to… | May 14, 2026 |
| CVE-2026-6474 | MEDIUM | 4.3 | 0.03% | — | 6.5 | Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server… | May 14, 2026 |
| CVE-2026-6474 | MEDIUM | 4.3 | 0.03% | — | 6.3 | Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server… | May 14, 2026 |
| CVE-2026-6474 | MEDIUM | 4.3 | 0.03% | — | 6.4 | Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server… | May 14, 2026 |
PostgreSQL 6.x is EOL — migrate to PostgreSQL 7.x
PostgreSQL 7.x is the next major release. Plan your upgrade before PostgreSQL 6.x stops receiving security patches.
Frequently asked questions
Is PostgreSQL 6 end of life?
Yes. All PostgreSQL 6.x releases have reached end of life and no longer receive security patches. There are 24 known CVEs affecting PostgreSQL 6.x. Migrate to PostgreSQL 7.x as soon as possible.
What CVEs affect PostgreSQL 6?
There are 24 CVEs tracked for PostgreSQL 6.x. See the full list above with CVSS and EPSS scores.
What is the latest PostgreSQL 6 version?
The latest PostgreSQL 6.x patch release is 6.5.3, released on November 4, 1999. Always run the latest patch to benefit from all security fixes.
How to migrate from PostgreSQL 6 to PostgreSQL 7?
To migrate from PostgreSQL 6 to PostgreSQL 7: (1) review the official PostgreSQL 7 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.
Is it safe to run PostgreSQL 6 in production?
No. PostgreSQL 6 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA