# CVE-2026-0603: Org.hibernate/hibernate-core: hibernate: information disclosure and data deletion via second-order sql injection

> A second-order SQL injection in Hibernate allows attackers to read sensitive data and delete database records when specific ID builders are used.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jan 2026
- **Updated:** 6 Oct 2026
- **Also known as:** CLSA-2026-1769731733, CLSA-2026-1778892379, CLSA-2026-1779151631, CLSA-2026-1779238047, CLSA-2026-1783299710, CLSA-2026-1783386136, ECHO-c80f-4ef7-93ad, GHSA-2p5w-cvg5-gc5c, ROOT-APP-MAVEN-CVE-2026-0603

## What is CVE-2026-0603?

CVE-2026-0603 is a high-severity SQL injection vulnerability in Red Hat RHEL-8 based Middleware Containers, published on 23 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-0603?

2 open source packages ship an affected version, including org.hibernate:hibernate-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.hibernate:hibernate-core` | Maven | From 5.2.8 | 5.3.38 |
| `org.hibernate:hibernate-core` | Maven | From 5.2.8 | 5.3.38 |

## How do I fix CVE-2026-0603?

Upgrade org.hibernate:hibernate-core to 5.3.38 or later.

## Is CVE-2026-0603 being exploited?

There is no known exploitation of CVE-2026-0603 in the wild and no public exploit code.

Public exploit code:

- Hibernate ORM Second-Order SQL Injection (github_poc): https://github.com/EQSTLab/CVE-2026-0603
- https://github.com/yym8538/CVE-2026-0603 (github_poc): https://github.com/yym8538/CVE-2026-0603

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0603 and fix it if it is affected.

What it is: CVE-2026-0603 is a high-severity SQL injection vulnerability in Red Hat RHEL-8 based Middleware Containers, published on 23 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-0603 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.hibernate:hibernate-core (Maven): affected from 5.2.8; fixed in 5.3.38
- org.hibernate:hibernate-core (Maven): affected from 5.2.8; fixed in 5.3.38

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-0603/ (Markdown: https://insights.sbomify.com/CVE-2026-0603/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0603
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0603
- OSV: https://osv.dev/vulnerability/CVE-2026-0603

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0603/
Summaries are generated and may contain mistakes; the official description above is the record.