How severe is GHSA-2p5w-cvg5-gc5c?

GHSA-2p5w-cvg5-gc5c has a CVSS score of 8.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2p5w-cvg5-gc5c?

GHSA-2p5w-cvg5-gc5c affects the following packages: org.hibernate:hibernate-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2p5w-cvg5-gc5c?

Update org.hibernate:hibernate-core to 5.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p5w-cvg5-gc5c is resolved across your whole dependency graph.

How do I detect GHSA-2p5w-cvg5-gc5c in my Maven dependencies?

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.

How do I mitigate GHSA-2p5w-cvg5-gc5c if there is no patch (or I can't update yet)?

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.

Is GHSA-2p5w-cvg5-gc5c actively exploited in the wild?

No public exploit code has been indexed for GHSA-2p5w-cvg5-gc5c 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-2p5w-cvg5-gc5c?

GHSA-2p5w-cvg5-gc5c has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th 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-2p5w-cvg5-gc5c?

GHSA-2p5w-cvg5-gc5c 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-2p5w-cvg5-gc5c published, and has it been updated?

GHSA-2p5w-cvg5-gc5c was published on January 23, 2026 and was last updated on October 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Hibernate vulnerable to SQL InjectionGHSA-2p5w-cvg5-gc5c

HIGHFix: hibernate/hibernate-orm@3f820fd

GHSA-2p5w-cvg5-gc5c is a high-severity (CVSS 8.3) SQL Injection vulnerability in org.hibernate:hibernate-core. A fix is available for org.hibernate:hibernate-core — see the affected versions and patch details below.

Also known asCVE-2026-0603

Published

Jan 23, 2026

Updated

Oct 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2p5w-cvg5-gc5c.

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

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 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.hibernate:hibernate-core`	≥ 5.2.8&&< 5.3.38	5.3.38`org.hibernate:hibernate-core:5.3.38`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.hibernate:hibernate-core to 5.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p5w-cvg5-gc5c is resolved across your whole dependency graph.
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 HatImportant

This vulnerability is rated Important for Red Hat products as it allows a remote attacker with low privileges to perform second-order SQL injection in applications using Hibernate's InlineIdsOrClauseBuilder with unsanitized non-alphanumeric characters in the ID column. This could lead to sensitive information…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-2p5w-cvg5-gc5c (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7	`eap7-hibernate-0:5.1.17-4.Final_redhat_00005.1.ep7.el7`	RHSA-2026:6012
Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7	`eap7-hibernate-0:5.3.38-1.Final_redhat_00001.1.el7eap`	RHSA-2026:6011
Red Hat JBoss Enterprise Application Platform 7.4.24	`org.hibernate/hibernate-core:5.3.38.Final-redhat-00001`	RHSA-2026:4924
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 7	`eap7-hibernate-0:5.3.38-1.Final_redhat_00001.1.el7eap`	RHSA-2026:4915
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 8	`eap7-hibernate-0:5.3.38-1.Final_redhat_00001.1.el8eap`	RHSA-2026:4916
Red Hat JBoss Enterprise Application Platform 7.4 ELS on RHEL 9	`eap7-hibernate-0:5.3.38-1.Final_redhat_00001.1.el9eap`	RHSA-2026:4917
Red Hat Single Sign-On 7.6.13	`hibernate-core`	RHSA-2026:76132
Red Hat Single Sign-On 7.6 for RHEL 7	`rh-sso7-keycloak-0:18.0.20-1.redhat_00001.1.el7sso`	RHSA-2026:76128

Frequently Asked Questions

O3 Security · Impact-Aware SCA

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

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works