Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2019-14900 — hibernate-core

MEDIUMFix: hibernate/hibernate-orm@3f3c1ab

CVE-2019-14900 is a medium-severity (CVSS 6.5) SQL Injection vulnerability in org.hibernate:hibernate-core. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.hibernate:hibernate-core — see the affected versions and patch details below.

SQL Injection in Hibernate ORM

Also known asGHSA-8grg-q944-cch5
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Oct 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs81th percentile — riskier than 81% of all scored CVEsHighest risk
1.20%1.67%2.15%2.63%1.8%2.1%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2019-14900 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

3 pkgs affected
☕org.hibernate:hibernate-core☕org.hibernate:hibernate-core☕org.hibernate:hibernate-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.hibernate:hibernate-coreall versions5.3.18org.hibernate:hibernate-core:5.3.18
☕Mavenorg.hibernate:hibernate-core≥ 5.4.0&&< 5.4.185.4.18org.hibernate:hibernate-core:5.4.18
☕Mavenorg.hibernate:hibernate-core≥ 5.5.0.Alpha1&&< 5.5.0.Beta15.5.0.Beta1org.hibernate:hibernate-core:5.5.0.Beta1

Affected Products

10 products · 21 configurations
Application
hibernate ormhibernate
≥ 5.4.0 && < 5.4.18
range
Application
quarkusquarkus
≤ 1.5.2
range
Application
build of quarkusredhat
all
Application
decision managerredhat
1 version
7.0
Application
fuseredhat
< 7.8.0
range
Application
jboss data gridredhat
1 version
7.0.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hibernate:hibernate-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.hibernate:hibernate-core to 5.3.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-14900 is resolved across your whole dependency graph.

  3. Workarounds

    Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

OpenDaylight: In RHOSP10, RHOSP13 and RHOSP14 editions of Red Hat OpenStack platform, the hibernate-jfa library shipped with OpenDaylight is contains a flaw in the processing of SQL queries. The hibernate-jha implemenation is not used in a vulnerable way in OpenDaylight, preventing the potential for SQL injection. Red…

Workaround published by Red Hat
There is no currently known mitigation for this flaw.
Source: Red Hat security advisory for CVE-2019-14900 (CC BY 4.0)
ProductFixed inAdvisory
EAP-CD 20 Tech Previewhibernate-coreRHSA-2020:3585
Red Hat build of Quarkus 1.7.5hibernate-coreRHSA-2020:4252
Red Hat Fuse 7.8.0hibernate-coreRHSA-2020:5568
Red Hat JBoss Enterprise Application Platform 7hibernate-coreRHSA-2020:3642
Red Hat JBoss Enterprise Application Platform 7hibernate-coreRHSA-2020:3464
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 6eap7-dom4j-0:2.1.3-1.redhat_00001.1.el6eapRHSA-2020:3637
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 7eap7-dom4j-0:2.1.3-1.redhat_00001.1.el7eapRHSA-2020:3638
Red Hat JBoss Enterprise Application Platform 7.2 for RHEL 8eap7-dom4j-0:2.1.3-1.redhat_00001.1.el8eapRHSA-2020:3639

Frequently Asked Questions

A flaw was found in Hibernate ORM in versions before 5.3.18, 5.4.18 and 5.5.0.Beta1. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SELECT or GROUP BY parts of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks.
O3 Security · Impact-Aware SCA

Is CVE-2019-14900 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2019-14900: hibernate-core — Fixed in 5.3.18