Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-2p5w-cvg5-gc5c

HIGH

GHSA-2p5w-cvg5-gc5c is a high-severity (CVSS 8.3) SQL Injection vulnerability in org.hibernate:hibernate-core. O3 Security confirms whether GHSA-2p5w-cvg5-gc5c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Hibernate vulnerable to SQL Injection

Also known asCVE-2026-0603
Published
Jan 23, 2026
Updated
Apr 17, 2026
Affected
1 pkg
Patched
None yet
Exploits
None indexed

Real-World Exposure

1 pkg affected
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. A remote attacker with low privileges could exploit a second-order SQL injection vulnerability by providing specially crafted, unsanitized non-alphanumeric characters in the ID column when the InlineIdsOrClauseBuilder is used. This could lead to sensitive information disclosure, such as reading system files, and allow for data manipulation or deletion within the application's database, resulting in an application level denial of service.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
Mavenorg.hibernate:hibernate-core5.2.8No fix

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. 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.

  2. Remediation status

    No patched version of org.hibernate:hibernate-core has shipped for GHSA-2p5w-cvg5-gc5c yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-2p5w-cvg5-gc5c 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-2p5w-cvg5-gc5c. 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. A remote attacker with low privileges could exploit a second-order SQL injection vulnerability by providing specially crafted, unsanitized non-alphanumeric characters in the ID column when the InlineIdsOrClauseBuilder is used. This could lead to sensitive information disclosure, such as reading system files, and allow for data manipulation or deletion within the application's database, resulting in an application level denial of service.
O3 Security · Impact-Aware SCA

Is GHSA-2p5w-cvg5-gc5c in your dependencies?

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