CVE-2026-0603
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA second-order SQL injection vulnerability exists in Hibernate's InlineIdsOrClauseBuilder. Attackers with low privileges can insert malicious non-alphanumeric characters into ID column values; these values are stored unsanitized and later incorporated into dynamically constructed SQL queries, potentially enabling arbitrary SQL execution, file system reads, and data manipulation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Hibernate usageSearch project dependencies (Maven pom.xml, Gradle build.gradle, or JAR files) for Hibernate ORM librariesAffected if Hibernate ORM is present in the application dependencies
-
Determine Hibernate versionCheck the Hibernate library version in your build configuration or JAR manifest; compare against any known vulnerable versions if available from vendor advisoriesAffected if Running an unpatched Hibernate version that contains the InlineIdsOrClauseBuilder vulnerability
-
Locate InlineIdsOrClauseBuilder usageSearch codebase for imports and references to org.hibernate.jpa.criteria InlineIdsOrClauseBuilder or its usage in query construction logic; check for criteria API or HQL/JPQL queries that handle multiple ID valuesAffected if Codebase uses InlineIdsOrClauseBuilder for building IN clauses with ID values
-
Audit ID input handlingReview code paths where user-supplied ID values are received, stored, and later used in Hibernate query construction; look for direct string concatenation or interpolation of ID values into queries without parameterizationAffected if ID values from external sources are stored and later used in dynamic SQL without sanitization or parameter binding
-
Check for unsanitized ID storageExamine database schema and application logic to determine if ID column values accept arbitrary input; verify if input validation exists before persisting ID dataAffected if Application allows storage of non-alphanumeric or special characters in ID fields that could be used for injection
User is affected if Hibernate with InlineIdsOrClauseBuilder is in use, user-supplied ID values can be stored without sanitization, and those values are later incorporated into dynamically built SQL queries without parameterization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Hibernate to a patched version that properly sanitizes or parameterizes inputs in InlineIdsOrClauseBuilder; implement strict input validation for all user-supplied ID values before storage and before use in SQL construction.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0603 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0603 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data