H2 Database · Lifecycle Status

H2 Database End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all H2 Database versions. Dates read at the vendor's own lifecycle pages (github.com). Updated at every deploy.

✓ H2 Database 2.5.252 is actively supported. No versions approaching EOL in the next 6 months.

H2 Database 2 is supported, with no end-of-life or end-of-support date announced yet. 1 of 2 tracked H2 Database versions is past end of life; the most recent to reach it, 1.4, did so on November 29, 2021. The full H2 Database lifecycle, with every version's release and end-of-support date, is in the table below.

Running an EOL version? Get matched with support options — free ↓
Latest Active
2.5.252
2 series
Next EOL
—
None upcoming
Active Versions
1
of 2 total
EOL Versions
1
no longer patched
50 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
40/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 →
CPE Identifier
cpe:2.3:a:h2database:h2
The Common Platform Enumeration name vulnerability scanners and CVE records use for H2 Database. Verified against the NIST CPE dictionary. Machine-readable for all products: cpe-map.json
Package URL (purl)
pkg:maven/com.h2database/h2
The package URL identifier SBOM tools emit for H2 Database, so a CycloneDX or SPDX component resolves to this page by exact identifier rather than by name. Machine-readable for all products: purl-map.json; whole-SBOM checks: POST /v1/sbom or the Stack Scanner.
Release Cycle Timeline
■ EOL   ■ Warning   ■ Active   ┊ Today
Release cycle timeline 20152016201720182019202020212022202320242025202620271.42TODAY
1 version of H2 Database is past end of life — security patches have stopped. Get matched with support →
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.4 1.4.200 Apr 12, 2014 Nov 29, 2021 1818 days past EOL EOL
2 2.5.252 Nov 29, 2021 TBD Supported Active
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.
H2 Database EOL status badge Live EOL badge for your README — updates automatically at every build. [![H2 Database EOL](https://img.shields.io/endpoint?url=https%3A%2F%2Fendoflife.ai%2Fbadge%2Fh2.json)](https://endoflife.ai/h2)

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 (the 2.x row above carries its newest release and date).

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.

H2 Database release and support pattern

Of the 2 release lines tracked, 1 is past end of life and 1 is still within support. The newest line, 2, was released November 29, 2021. No end-of-life date is currently published for the 1 supported line.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

What does H2 Database end of life mean for your organization?

When a version of H2 Database reaches end of life, the vendor's standard security patches for that version stop. Vulnerabilities found after that date are still published on the National Vulnerability Database, exploit code often becomes public, and systems on that version stay exposed until they are upgraded or covered by extended support.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but the vendor's policy provides no patch for the ended version. This is one of the most dangerous gaps 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.

Your options when H2 Database reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

OptionBest whenWatch out for
Move to a supported version The system will outlive the current version's support window and you can schedule the work Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits
Replace the component The project is unmaintained, or a better-supported alternative exists The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem
Buy extended support Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application A bridge, not a destination — every year purchased is a year the migration still has to happen
Document accepted risk The system is isolated, short-lived, or scheduled for retirement Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.

Extended Support Options

If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your H2 Database version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Get H2 Database Support Options

H2 Database has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for H2 Database is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."

Free · No obligation · Independent — we track the dates, vendors don't pay for placement · Dates verified against vendor sources
Frequently Asked Questions
What is the end-of-life date for H2 Database?
See the full table above for all H2 Database version EOL dates.
When is the H2 Database support end date?
Each H2 Database version has its own support end date — see the table above for every version's date.
What is the latest supported version of H2 Database?
The latest active version of H2 Database is 2.5.252. Always verify against the table above as support windows can change.
What happens when H2 Database reaches end of life?
When H2 Database reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor patch path — a growing attack surface that a CVE-based scan does not show. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give the date in advance.
How do I check if I'm running an EOL version of H2 Database?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL H2 Database versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

✓ 3 of 3 lifecycle dates vendor-sourced · confidence: 0 high, 3 medium, 0 low (each version page shows where every date comes from) · provenance · Source: the vendor's own lifecycle pages (github.com) · Generated at build time · How we source data →
H2 Database end-of-life status badge