Pgadmin 4 · Version Status
Pgadmin 4 End of Life Date
Pgadmin 4 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.
⚠
Pgadmin 4 is past end of life. This version no longer receives security patches. 2055 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 25, 2021
2055 days past EOL
Latest Release
4.30
Standard release
Release Date
Jan 10, 2019
Pgadmin 4 series
Lifecycle detail
Pgadmin 4 was released on January 10, 2019 and support ended on February 25, 2021 — a supported lifespan of 2 years and 2 months, longer than the 1 year median for Pgadmin releases. The last patch it will ever receive is 4.30, published January 28, 2021 — 28 days before support ended. It has been without security patches for 5 years and 8 months. 4 newer Pgadmin releases have 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 Pgadmin 4 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.6 |
Oct 5, 2017 |
EOL |
| 2 |
2.1 |
Apr 13, 2018 |
EOL |
| 3 |
3.6 |
Jan 10, 2019 |
EOL |
| → 4 |
4.30 |
Feb 25, 2021 |
EOL |
| 5 |
5.7 |
Oct 7, 2021 |
EOL |
| 6 |
6.21 |
Apr 13, 2023 |
EOL |
| 7 |
7.8 |
Nov 23, 2023 |
EOL |
| 8 |
8.14 |
Feb 6, 2025 |
EOL |
What does Pgadmin 4 end of life mean?
When Pgadmin 4 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 Pgadmin 4 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Pgadmin 9 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Pgadmin 4 reach end of life?
Pgadmin 4 reached end of life on February 25, 2021. This version is no longer receiving security patches.
Is Pgadmin 4 still supported?
No. Pgadmin 4 reached end of life on February 25, 2021 and is no longer receiving security patches.
What should I upgrade to from Pgadmin 4?
The recommended upgrade from Pgadmin 4 is
Pgadmin 9 — the latest actively supported version. Check the
Pgadmin full timeline for all supported versions.
What are the security risks of running Pgadmin 4 past EOL?
When Pgadmin 4 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 Pgadmin should migrate immediately or implement compensating controls.