Liquibase 4 · Version Status

Liquibase 4 End of Life Date

Liquibase 4 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Liquibase 4 is past end of life. This version no longer receives security patches. 312 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 30, 2025
312 days past EOL
Latest Release
4.33.0
Standard release
Release Date
Jul 13, 2020
Liquibase 4 series
Lifecycle detail

Liquibase 4 was released on July 13, 2020 and support ended on September 30, 2025 — a supported lifespan of 5 years and 3 months. The last patch it will ever receive is 4.33.0, published July 9, 2025 — 3 months before support ended. It has been without security patches for 10 months.

All Liquibase versions Liquibase 5 →
40 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
30/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 →
Recommended upgrade path
Liquibase 5
Latest release: 5.0.3 · EOL: Supported
View full Liquibase timeline →
Extended Support
Extended Liquibase 4 support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Liquibase Versions
VersionLatestEOL DateStatus
4 4.33.0 Sep 30, 2025 EOL
5 5.0.3 EOL Active

What does Liquibase 4 end of life mean?

When Liquibase 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Liquibase 4 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Liquibase 5 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Liquibase 4 reach end of life?
Liquibase 4 reached end of life on September 30, 2025. This version is no longer receiving security patches.
Is Liquibase 4 still supported?
No. Liquibase 4 reached end of life on September 30, 2025 and is no longer receiving security patches.
What should I upgrade to from Liquibase 4?
The recommended upgrade from Liquibase 4 is Liquibase 5 — the latest actively supported version. Check the Liquibase full timeline for all supported versions.
What are the security risks of running Liquibase 4 past EOL?
When Liquibase 4 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Liquibase should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →