Quick answers
- Is CVE-2026-82045 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82045 being exploited in the wild.
- How severe is CVE-2026-82045?
- Medium severity, with a CVSS score of 6.5, published 2 October 2026.
- Which products and versions are affected?
- UTMStack before 11.2.16.
- Is there a fix for CVE-2026-82045?
- Yes: fixed in 11.2.16. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82045 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-82045?
- Check whether you run UTMStack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 11.2.16
Technical details
UtmNetworkScanService.searchPropertyValues() in UTMStack constructs JPQL queries using String.format() without parameter binding, allowing authenticated attackers to inject malicious JPQL through the value parameter of the GET /api/utm-network-scans/searchPropertyValues endpoint. The vulnerability requires prior authentication and enables arbitrary entity data extraction from the underlying database. The fix parameterizes the vulnerable query using bound parameters (:value).
Affected products
- UTMStack UTMStack before 11.2.16
Timeline
- 2026-10-02: disclosed
- 2026-10-01: patched