# CVE-2026-82045: UTMStack < 11.2.16 JPQL Injection via searchPropertyValues

> Authenticated attackers can exploit JPQL injection in UTMStack to read arbitrary entity data, including sensitive credential tables.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 2 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-ggxr-hwjj-pgmj

## What is CVE-2026-82045?

CVE-2026-82045 is a high-severity SQL injection vulnerability in UTMStack, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

UTMStack before 11.2.16 contains a JPQL injection vulnerability that allows authenticated attackers to read arbitrary entity data by exploiting UtmNetworkScanService.searchPropertyValues(), which builds a JPQL query with String.format() and executes it via em.createQuery() without parameter binding. Attackers can inject malicious JPQL through the value parameter in the GET /api/utm-network-scans/searchPropertyValues endpoint to extract sensitive data including credential tables such as jhi_user.

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

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


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

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

## Is CVE-2026-82045 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82045 is a high-severity SQL injection vulnerability in UTMStack, published on 2 Oct 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-82045 in the wild and no public exploit code.

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

## Sources

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

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