CVE-2026-0603: Org.hibernate/hibernate-core: hibernate: information disclosure and data deletion via second-order sql injection
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-0603 is a high-severity Hibernate flaw where crafted data stored in an ID column can later trigger SQL injection in certain query-building paths. A low-privileged remote user could cause sensitive data exposure, database changes, deletion, or application-level denial of service.
Executive priority
Treat this as a high-priority remediation item for affected enterprise Java platforms. It can affect confidentiality and integrity, but the provided evidence does not show active exploitation. Prioritize internet-facing or broadly authenticated applications first, then internal systems using affected Red Hat product streams.
Technical view
The flaw is a second-order SQL injection in Hibernate when InlineIdsOrClauseBuilder is used with specially crafted, unsanitized non-alphanumeric characters in an ID column. The CVSS is 8.3, with network attack vector, low complexity, low privileges, no user interaction, and high confidentiality and integrity impact.
Likely exposure
Exposure is most likely in Java applications using affected Hibernate Core through listed Red Hat products, especially JBoss EAP 7 streams, AMQ Broker 7, Fuse 7, and OptaPlanner 8. Products marked unaffected in the bundle should still be verified against Red Hat VEX or vendor inventory.
Exploitation context
The source bundle does not show KEV listing or cited active exploitation. The attack requires low privileges and a code path where attacker-controlled ID values are persisted and later processed by the vulnerable Hibernate builder. Evidence supports serious potential impact, not confirmed exploitation in the wild.
Researcher notes
The key exposure condition is second-order behavior: malicious input may be stored first and trigger later during Hibernate query construction. Avoid assuming every Hibernate deployment is exploitable; verify product status, package version, and whether vulnerable query-building behavior is reachable.
Mitigation direction
Apply the relevant Red Hat security advisories for affected supported products.
Check Red Hat CVE and CSAF VEX status for each deployed product version.
Upgrade Hibernate-containing products only according to vendor-supported guidance.
Review application handling of attacker-controlled ID values for sanitization assumptions.
Prioritize systems exposing authenticated low-privilege workflows backed by affected Hibernate components.
Validation and detection
Inventory Hibernate Core versions and Red Hat product packages across Java applications.
Map deployed products against the affected and unaffected entries in the source bundle.
Identify code paths that persist user-controlled ID values later used in Hibernate queries.
Confirm whether InlineIdsOrClauseBuilder-related paths exist in affected application flows.
After patching, run regression tests around ID handling and database update/delete workflows.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
10Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.