How severe is GHSA-j8jw-g6fq-mp7h?

GHSA-j8jw-g6fq-mp7h has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-j8jw-g6fq-mp7h?

GHSA-j8jw-g6fq-mp7h affects the following packages: org.hibernate:hibernate-core (Maven), org.hibernate:hibernate-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j8jw-g6fq-mp7h?

Update org.hibernate:hibernate-core to 5.4.24.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8jw-g6fq-mp7h is resolved across your whole dependency graph.

How do I detect GHSA-j8jw-g6fq-mp7h in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hibernate:hibernate-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-j8jw-g6fq-mp7h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-j8jw-g6fq-mp7h?

O3 pinpoints whether GHSA-j8jw-g6fq-mp7h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-j8jw-g6fq-mp7h actively exploited in the wild?

No public exploit code has been indexed for GHSA-j8jw-g6fq-mp7h yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j8jw-g6fq-mp7h?

GHSA-j8jw-g6fq-mp7h has an EPSS (Exploit Prediction Scoring System) score of 2.9%, placing it in the 85th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j8jw-g6fq-mp7h?

GHSA-j8jw-g6fq-mp7h is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-j8jw-g6fq-mp7h published, and has it been updated?

GHSA-j8jw-g6fq-mp7h was published on February 9, 2022 and was last updated on June 27, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-j8jw-g6fq-mp7h: SQL injection in hibernate-core (High 7.4)

EPSS Exploitation Probability

via FIRST.org ↗

2.9%probability of exploitation in next 30 days

Lower Risk85th percentile+2.23%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕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-core in versions prior to 5.3.20.Final and in 5.4.0.Final up to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.hibernate:hibernate-core`	≥ 5.4.0.Final&&< 5.4.24.Final	5.4.24.Final
☕Maven	`org.hibernate:hibernate-core`	all versions	5.3.20.Final

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hibernate:hibernate-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.hibernate:hibernate-core to 5.4.24.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8jw-g6fq-mp7h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-j8jw-g6fq-mp7h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-j8jw-g6fq-mp7h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was found in hibernate-core in versions prior to 5.3.20.Final and in 5.4.0.Final up to and including 5.4.23.Final. A SQL injection in the implementation of the JPA Criteria API can permit unsanitized literals when a literal is used in the SQL comments of the query. This flaw could allow an attacker to access unauthorized information or possibly conduct further attacks. The highest threat from this vulnerability is to data confidentiality and integrity.

O3 Security · Impact-Aware SCA

Is GHSA-j8jw-g6fq-mp7h in your dependencies?

O3 detects GHSA-j8jw-g6fq-mp7h across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-j8jw-g6fq-mp7h