PostgreSQL 10.x — End of Life
EOL High riskPostgreSQL 10.x reached end of life on Nov 10, 2022, 1427 days ago, and no longer receives security fixes. The most recent release in this series is 10.23. 8 CVEs are tracked for this series. 8 of them were published after the end of life of the affected cycle and will not get an official patch. The next major version is PostgreSQL 11. See PostgreSQL 11 →
PostgreSQL 10.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status | Alert me |
|---|---|---|---|---|---|---|
| 10 | Oct 5, 2017 | — | Nov 10, 2022 | 10.23 | EOL |
CVEs affecting PostgreSQL 10.x (8)
| CVE | Severity | CVSS | EPSS | KEV | Cycle | Description | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-6637 | HIGH | 8.8 | 0.37% | — | 10 | 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.59% | — | 10 | 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.55% | — | 10 | Covert timing channel in comparison of MD5-hashed password in PostgreSQL authentication allows an attacker to recover us… | May 14, 2026 |
| CVE-2026-6477 | HIGH | 8.8 | 0.45% | — | 10 | Use of inherently dangerous function PQfn(..., result_is_int=0, ...) in PostgreSQL libpq lo_export(), lo_read(), lo_lsee… | May 14, 2026 |
| CVE-2026-6475 | HIGH | 8.8 | 0.32% | — | 10 | Symlink following in PostgreSQL pg_basebackup plain format and in pg_rewind allows an origin superuser to overwrite loca… | May 14, 2026 |
| CVE-2026-6474 | MEDIUM | 4.3 | 0.31% | — | 10 | Externally-controlled format string in PostgreSQL timeofday() function allows an attacker to retrieve portions of server… | May 14, 2026 |
| CVE-2026-6473 | HIGH | 8.8 | 1.00% | — | 10 | Integer wraparound in multiple PostgreSQL server features allows an unprivileged database user to cause the server to un… | May 14, 2026 |
| CVE-2026-6472 | MEDIUM | 5.4 | 0.23% | — | 10 | Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to… | May 14, 2026 |
PostgreSQL 10.x is EOL — migrate to PostgreSQL 11.x
PostgreSQL 11.x is the next major release. Plan your upgrade before PostgreSQL 10.x stops receiving security patches.
Add a PostgreSQL 10 EOL badge to your README
Show your users which PostgreSQL version your project runs and whether it is still supported. The badge updates automatically. More formats and options →
[](https://eolcanary.com/explore/postgresql/10)Frequently asked questions
Is PostgreSQL 10 end of life?
Yes. All PostgreSQL 10.x releases have reached end of life and no longer receive security patches. There are 8 known CVEs affecting PostgreSQL 10.x. Migrate to PostgreSQL 11.x as soon as possible.
What CVEs affect PostgreSQL 10?
There are 8 CVEs tracked for PostgreSQL 10.x. See the full list above with CVSS and EPSS scores.
What is the latest PostgreSQL 10 version?
The latest PostgreSQL 10.x patch release is 10.23, released on November 7, 2022. Always run the latest patch to benefit from all security fixes.
How to migrate from PostgreSQL 10 to PostgreSQL 11?
To migrate from PostgreSQL 10 to PostgreSQL 11: (1) review the official PostgreSQL 11 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 10 in production?
No. PostgreSQL 10 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