CloudNativePG 1.24 · Version Status
CloudNativePG 1.24 End of Life Date
CloudNativePG 1.24 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (cloudnative-pg.io); the source of each date is on the product page.
⚠
CloudNativePG 1.24 is past end of life. This version no longer receives security patches. 512 days past EOL — migrate to a supported version immediately.
EOL Date
May 23, 2025
512 days past EOL
Latest Release
1.24.4
Standard release
Release Date
Aug 22, 2024
CloudNativePG 1.24 series
Lifecycle detail
CloudNativePG 1.24 was released on August 22, 2024 and support ended on May 23, 2025 — a supported lifespan of 9 months, longer than the 7 months median for CloudNativePG releases. The last patch it will ever receive is 1.24.4, published May 23, 2025 — on the day support ended. It has been without security patches for 1 year and 5 months. 4 newer CloudNativePG 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 CloudNativePG 1.24 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All CloudNativePG Versions
| Version | Latest | EOL Date | Status |
|---|
| 1.15 |
1.15.5 |
Oct 6, 2022 |
EOL |
| 1.16 |
1.16.5 |
Dec 21, 2022 |
EOL |
| 1.17 |
1.17.5 |
Mar 20, 2023 |
EOL |
| 1.18 |
1.18.5 |
Jun 12, 2023 |
EOL |
| 1.19 |
1.19.6 |
Nov 3, 2023 |
EOL |
| 1.20 |
1.20.6 |
Jan 21, 2024 |
EOL |
| 1.21 |
1.21.6 |
Jun 12, 2024 |
EOL |
| 1.22 |
1.22.5 |
Jul 24, 2024 |
EOL |
What does CloudNativePG 1.24 end of life mean?
When CloudNativePG 1.24 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 CloudNativePG 1.24 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to CloudNativePG 1.30 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does CloudNativePG 1.24 reach end of life?
CloudNativePG 1.24 reached end of life on May 23, 2025. This version is no longer receiving security patches.
Is CloudNativePG 1.24 still supported?
No. CloudNativePG 1.24 reached end of life on May 23, 2025 and is no longer receiving security patches.
What should I upgrade to from CloudNativePG 1.24?
The recommended upgrade from CloudNativePG 1.24 is
CloudNativePG 1.30 — the latest actively supported version. Check the
CloudNativePG full timeline for all supported versions.
What are the security risks of running CloudNativePG 1.24 past EOL?
When CloudNativePG 1.24 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 CloudNativePG should migrate immediately or implement compensating controls.