CloudNativePG 1.30 · Version Status

CloudNativePG 1.30 End of Life Date

CloudNativePG 1.30 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.30 is actively supported. No end-of-life date has been announced yet.
EOL Date
TBD
Supported
Latest Release
1.30.1
Standard release
Release Date
Jun 29, 2026
CloudNativePG 1.30 series
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

CloudNativePG 1.30 was released on June 29, 2026 and has no published end-of-life date yet. Its most recent patch is 1.30.1, published September 23, 2026.

← CloudNativePG 1.29 All CloudNativePG versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
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 →
All CloudNativePG Versions
VersionLatestEOL DateStatus
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.30 end of life mean?

When CloudNativePG 1.30 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.30 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.30 reach end of life?
CloudNativePG 1.30 has no announced end-of-life date yet — it is currently supported, with EOL to be determined.
Is CloudNativePG 1.30 still supported?
Yes, CloudNativePG 1.30 is currently supported. The EOL date is TBD.
What should I upgrade to from CloudNativePG 1.30?
The recommended upgrade from CloudNativePG 1.30 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.30 past EOL?
When CloudNativePG 1.30 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.
Data from the vendor's own lifecycle pages (cloudnative-pg.io) · Generated at build time · How we source data →