H2 Database End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all H2 Database versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.4 | 1.4.200 | Apr 12, 2014 | Nov 29, 2021 | 1682 days past EOL | EOL |
| 2 | 2.4.240 | Nov 29, 2021 | TBD | Supported | Active |
H2 Database lifecycle status — the real story
H2 is the JVM's most common embedded database — the default for local development, testing, and a surprising amount of quietly shipped production software. Its lifecycle split at the 2.0 release in November 2021: the 1.4.x line ended at 1.4.200 (October 2019) and is unsupported, while 2.x remains actively maintained (2.4.240 shipped September 2025).
The split matters for security: critical vulnerabilities disclosed in early 2022 — including a JNDI-based remote-code-execution flaw in the H2 console (CVE-2021-42392, found in the wake of Log4Shell) — affect the 1.x era and will never be patched there. H2 2.x also changed the on-disk format, so upgrading is a data-migration exercise, not a version bump.
That migration friction is why 1.4.200, a 2019 release, still ranks among the most-downloaded H2 artifacts — a textbook stranded-version problem worth flagging in any Java dependency audit.
What does H2 Database end of life mean for your organization?
When a version of H2 Database reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL H2 Database should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL H2 Database versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →