HIBERNATE ORM COVERAGE
Hibernate ORM 5.3 and 6.2 are end of life. Your patching does not have to be.
Hibernate ORM 5.3, 6.2, 7.1 and 7.3 are end of life, and 6.6 and 7.2 are in limited support, where the project says backports are highly restricted and releases are not guaranteed. The project maintains only the latest stable series, 7.4. OSSeva patches Hibernate ORM 5.3, 6.2, 6.6 and 7.1 to 7.3, with Critical fixes within 48 hours.
| Who it is for | Teams running Hibernate ORM 5.3, 6.x or 7.1 to 7.3, directly or inside Spring, Quarkus or an application server, that cannot move to 7.4 yet |
|---|---|
| What you get | Signed patched builds on the series you run, with mappings, HQL and Java version unchanged. Assure adds an inventory of Hibernate versions and an upgrade plan. |
| How it is priced | Per application. Ask for a quote. |
| What happens next | You send your work email, we confirm your Hibernate series and how it is packaged, and you get a coverage plan. |
Reply within 1 business day · No commitment · or book a 15-minute call
Last reviewed
Trusted globally by enterprises





Hibernate ORM support status by series, read on 19 November 2026
Labels and last releases are from hibernate.org. The last column is endoflife.date's end of stable support, which for 6.6 and 7.2 is the date they moved to limited support.
| Series | Java versions | hibernate.org label | Last release listed | Stable support ended |
|---|---|---|---|---|
| 7.4 | 17, 21, 25 or 26 | Latest stable | 7.4.17.Final (19 Nov 2026) | Not ended |
| 7.3 | 17, 21, 25 or 26 | End of life | 7.3.13.Final (2 Aug 2026) | 7 Jun 2026 |
| 7.2 | 17, 21 or 25 | Limited support | 7.2.26.Final (19 Nov 2026) | 9 Jun 2026 |
| 7.1 | 17, 21 or 25 | End of life | 7.1.36.Final (17 Sep 2026) | 7 Jun 2026 |
| 6.6 | 11, 17, 21 or 25 | Limited support | 6.6.59.Final (18 Oct 2026) | 9 Jun 2026 |
| 6.2 | 11, 17, 20 or 21 | End of life | 6.2.52.Final (3 May 2026) | 3 May 2026 |
| 5.3 | 8, 11 or 17 | End of life | 5.3.39.Final (29 Jun 2026) | 19 Jan 2026 |
hibernate.org also lists 8.0 as the development series, with 8.0.0.CR1 on 12 November 2026. Java versions are from endoflife.date.
Hibernate ORM releases →Hibernate maintenance policy →Hibernate end-of-life support page →endoflife.date Hibernate ORM data →
What the one-series policy means for 5.3, 6.2 and 6.6
Hibernate is maintained one series at a time, so every older series is on its own the day a newer one becomes stable. The release table shows what that costs an application that has not moved.
- Series 5.3, 6.x and 7.x sit on different platforms. endoflife.date lists Jakarta EE 8 for 5.3, Jakarta EE 10 for 6.x and Jakarta EE 11 for 7.x. hibernate.org describes 5.3 as JPA 2.2, 5.5 as the first series with Jakarta JPA support, 6.2 as Jakarta Persistence 3.1 and 7.0 as Jakarta Persistence 3.2 with Java 17.
- Java is the second constraint. 5.3 runs on Java 8, 11 and 17. Every 7.x series needs Java 17 or later, so a 5.3 application on Java 8 changes both the runtime and the ORM at once.
- A limited-support series can still receive releases, but the policy does not promise them. 6.6.59.Final came out on 18 October 2026 and 7.2.26.Final on 19 November 2026. Plan as if a given fix may not arrive.
- An end-of-life label does not always mean releases stopped on that date. hibernate.org lists 5.3.39.Final on 29 June 2026 and 7.1.36.Final on 17 September 2026, after endoflife.date's end of stable support for both. Treat the last release as the real end of fixes.
- Advisories can skip a series. The one published hibernate-orm advisory, GHSA-834x-qc2r-wc59, lists fixes in 7.1.36, 7.2.25 and 7.4.9 and no 7.3 release, because 7.3.13 was released on 2 August 2026, before it. It says 6.x and earlier are unaffected, and that only applications that enable the incubating JSON HQL functions are exposed.
- Hibernate often arrives inside something else. hibernate.org lists Red Hat JBoss EAP and the Red Hat and IBM builds of Quarkus as long-term support offerings that cover Hibernate ORM, so the version to patch can be set by the framework or server, not by your own build file.
The CVE record for GHSA-834x-qc2r-wc59 is filed by IBM against IBM Enterprise Build of Quarkus and does not give Hibernate ranges, so the CVE id is not listed here. Sources: hibernate.org releases, maintenance policy and long-term support pages, the hibernate-orm GitHub advisories and endoflife.date, read on 19 November 2026.
Quarkus support →Spring Boot support →Spring Framework support →Java versions and end dates →
Why now
Hibernate maintains one series
The Hibernate maintenance policy says the team commits only to the latest stable series, now 7.4, and that there is no official long-term community support. Series 7.2 and 6.6 are labelled limited support, where backports are highly restricted and releases are not guaranteed.
Six series left stable support in 2026
endoflife.date records the end of stable support for 5.3 on 19 January 2026, 6.2 on 3 May, 7.1 and 7.3 on 7 June, and 6.6 and 7.2 on 9 June. hibernate.org labels 5.3, 6.2, 7.1 and 7.3 end-of-life, and 6.2 had its last release, 6.2.52.Final, on 3 May 2026.
Each major version is a different platform
endoflife.date lists Java 8, 11 or 17 and Jakarta EE 8 for 5.3, Java 11 to 21 and Jakarta EE 10 for 6.2 and 6.6, and Java 17 and later with Jakarta EE 11 for 7.x. Moving a long-lived application is a platform change, not a library bump.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 5.3(Community EOL 19 Jan 2026) | EOL | See advisories |
| 6.2(Community EOL 3 May 2026) | EOL | See advisories |
| 6.6(Limited support since 9 Jun 2026) | Extended | See advisories |
| 7.1(Community EOL 7 Jun 2026) | EOL | See advisories |
| 7.2(Limited support since 9 Jun 2026) | Extended | See advisories |
| 7.3(Community EOL 7 Jun 2026) | EOL | See advisories |
| 7.4(Latest stable series. Assessed case by case.) | Current | See advisories |
Running a Hibernate ORM version or build not listed here?
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Security patches for Hibernate ORM 5.3, 6.2, 6.6 and 7.1 to 7.3.
- Backported security fixes for Hibernate ORM 5.3, 6.2, 6.6 and 7.1 to 7.3
- Critical CVEs fixed within 48 hours, High within 7 days
- Signed artifacts (GPG + Sigstore)
- CVE disclosure notifications
- Architecture review
- 24/7 managed operations
OSSeva Assure
Patch plus compliance documentation and a Hibernate upgrade plan.
- Everything in Patch
- Inventory of Hibernate ORM versions across applications, including those bundled by frameworks
- Upgrade path assessment from 5.3 or 6.x to 7.4
- SOC 2 / HIPAA attestation package
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.
- Everything in Assure
- 24/7 application and database monitoring
- 15-minute P1 incident response SLA
- Named senior engineer on your account
All tiers priced per cluster/application — not per core.
Is Hibernate ORM 5.3 end of life?
Yes. hibernate.org labels the 5.3 series end-of-life, and endoflife.date records the end of stable support on 19 January 2026. The last release listed on hibernate.org is 5.3.39.Final, from 29 June 2026.
Is Hibernate ORM 6.2 end of life?
Yes. hibernate.org labels 6.2 end-of-life, and its last release, 6.2.52.Final, came out on 3 May 2026, the same day endoflife.date records as the end of stable support.
What does limited support mean for Hibernate 6.6 and 7.2?
The Hibernate maintenance policy says limited support sits between stable and end-of-life: backports are highly restricted and releases are not guaranteed. The project recommends upgrading or looking for paid support. hibernate.org lists 6.6 and 7.2 as limited support, with 6.6.59.Final on 18 October 2026.
Which Hibernate ORM versions does OSSeva patch?
Hibernate ORM 5.3, 6.2, 6.6 and 7.1 to 7.3, which left stable support in 2026. Other versions are assessed case by case through a version coverage check.
Does Hibernate have long-term support?
Not from the project. The Hibernate maintenance policy says there is no official long-term community support for Hibernate projects, and that older series may still get some bugfixes contributed through commercial long-term support. hibernate.org lists the commercial offerings it knows of, including IBM and Red Hat builds of Quarkus and Red Hat JBoss EAP.
Is there a known vulnerability in Hibernate ORM 7.3?
One GitHub advisory is published for hibernate-orm, GHSA-834x-qc2r-wc59 of 28 September 2026, on the incubating JSON HQL functions in 7.0.0.Beta2 and later. It lists fixes in 7.1.36, 7.2.25 and 7.4.9 and no 7.3 release, and the last 7.3 release, 7.3.13, came out on 2 August 2026. It says applications on 6.x and earlier are unaffected, and it applies only when hibernate.query.hql.json_functions_enabled is true.
How fast are Hibernate vulnerabilities patched?
Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.
How is OSSeva Hibernate support priced?
It is priced per application. Request a quote and a senior engineer replies within 1 business day.
Get a quote
Ready to get Hibernate ORM patched and supported?
Tell us your Hibernate ORM versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?