PostgreSQL 16.x — End of Life
Active High riskPostgreSQL 16.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 16 | Sep 14, 2023 | — | Nov 9, 2028 | 16.14 | Active |
CVEs affecting PostgreSQL 16.x (9)
| CVE | Severity | CVSS | EPSS | KEV | Cycle | Description | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-6473 | HIGH | 8.8 | 0.07% | — | 16 | Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to un… | May 14, 2026 |
| CVE-2026-6637 | HIGH | 8.8 | 0.04% | — | 16 | Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as th… | May 14, 2026 |
| CVE-2026-6475 | HIGH | 8.8 | 0.05% | — | 16 | 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% | — | 16 | Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lsee… | May 14, 2026 |
| CVE-2026-6479 | HIGH | 7.5 | 0.02% | — | 16 | 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% | — | 16 | 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% | — | 16 | 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% | — | 16 | Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server… | May 14, 2026 |
| CVE-2026-6638 | LOW | 3.7 | 0.02% | — | 16 | SQL injection in PostgreSQL logical replication ALTER SUBSCRIPTION ... REFRESH PUBLICATION allows a subscriber table cre… | May 14, 2026 |
PostgreSQL 16.x will reach end of life — migrate to PostgreSQL 17.x
PostgreSQL 17.x is the next major release. Plan your upgrade before PostgreSQL 16.x stops receiving security patches.
Frequently asked questions
Is PostgreSQL 16 end of life?
No. PostgreSQL 16.x is still supported until November 9, 2028. It continues to receive security patches and bug fixes.
What CVEs affect PostgreSQL 16?
There are 9 CVEs tracked for PostgreSQL 16.x. See the full list above with CVSS and EPSS scores.
What is the latest PostgreSQL 16 version?
The latest PostgreSQL 16.x patch release is 16.14, released on May 11, 2026. Always run the latest patch to benefit from all security fixes.
How to migrate from PostgreSQL 16 to PostgreSQL 17?
To migrate from PostgreSQL 16 to PostgreSQL 17: (1) review the official PostgreSQL 17 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 16 in production?
PostgreSQL 16 is still supported and safe for production use until November 9, 2028. Ensure you are running the latest patch version (16.14) to have all security fixes applied.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA