# CVE-2026-111390: Erupt through 2.3.0 HQL Injection via linkTreeVal in Data Table API

> Authenticated attackers can inject HQL to bypass data filters and read unauthorized entity data in the Erupt admin framework.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-qh8g-m9r5-r3mw

## What is CVE-2026-111390?

CVE-2026-111390 is a medium-severity SQL injection vulnerability in erupts erupt, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Erupt through 2.3.0 contains an HQL injection vulnerability that allows authenticated users to bypass tree-scoped data filters by injecting unescaped quotes into the linkTreeVal parameter of POST /erupt-api/data/table/{erupt}. Attackers holding query permission on entities with String-keyed linkTree targets can append always-true OR clauses or boolean subqueries to read data from other mapped entities.

Weakness: CWE-564 (Use of Hibernate with HQL/SQL Query String Containing External Input)

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


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

No fix has been published for CVE-2026-111390 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111390 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111390 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111390 is a medium-severity SQL injection vulnerability in erupts erupt, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111390 exists.

Affected product: erupts erupt. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111390/ (Markdown: https://insights.sbomify.com/CVE-2026-111390/index.md)
```

## Sources

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

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