Heroku Postgres 14 · Version Status
Heroku Postgres 14 End of Life Date
Heroku Postgres 14 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Heroku Postgres 14 is past end of life. This version no longer receives security patches. 320 days past EOL — migrate to a supported version immediately.
EOL Date
Nov 28, 2025
320 days past EOL
Latest Release
—
Standard release
Release Date
Mar 23, 2022
Heroku Postgres 14 series
Lifecycle detail
Heroku Postgres 14 was released on March 23, 2022 and support ended on November 28, 2025 — a supported lifespan of 3 years and 8 months, in line with the 4 years median for Heroku Postgres releases. It has been without security patches for 11 months. 1 newer Heroku Postgres release has shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Heroku Postgres 14 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Heroku Postgres Versions
| Version | Latest | EOL Date | Status |
|---|
| 11 |
— |
Jan 10, 2024 |
EOL |
| 12 |
— |
May 30, 2024 |
EOL |
| 13 |
— |
Oct 29, 2024 |
EOL |
| → 14 |
— |
Nov 28, 2025 |
EOL |
| 15 |
— |
Feb 28, 2027 |
Warning |
| 16 |
— |
EOL |
Active |
| 17 |
— |
EOL |
Active |
| 18 |
— |
EOL |
Active |
What does Heroku Postgres 14 end of life mean?
When Heroku Postgres 14 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Heroku Postgres 14 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Heroku Postgres 18 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Heroku Postgres 14 reach end of life?
Heroku Postgres 14 reached end of life on November 28, 2025. This version is no longer receiving security patches.
Is Heroku Postgres 14 still supported?
No. Heroku Postgres 14 reached end of life on November 28, 2025 and is no longer receiving security patches.
What should I upgrade to from Heroku Postgres 14?
The recommended upgrade from Heroku Postgres 14 is
Heroku Postgres 18 — the latest actively supported version. Check the
Heroku Postgres full timeline for all supported versions.
What are the security risks of running Heroku Postgres 14 past EOL?
When Heroku Postgres 14 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Heroku Postgres should migrate immediately or implement compensating controls.