Skip to main content
VulnerabilityPublished

CVE-2026-82045: UTMStack before 11.2.16 contains a JPQL injection vulnerability that allows authenticated attackers to read arbitrary entity data by exploiting

Affects utmstackSource GCVE Database

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 11.2.16 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 11.2.16
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade utmstack/utmstack to 11.2.16.

Affected software

ProductAffectedFixed in
GitHubutmstack/utmstackpkg:github/utmstack/utmstackOther threatsAffected
  • <11.2.16
Fixed in
  • 11.2.16

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to the affected endpoint to trusted users and monitor for suspicious activity related to JPQL injection attempts.

Description

UTMStack versions prior to 11.2.16 have a JPQL injection vulnerability in the UtmNetworkScanService.searchPropertyValues() method. Authenticated attackers can exploit this flaw by injecting malicious JPQL through the value parameter in the GET /api/utm-network-scans/searchPropertyValues endpoint. This allows unauthorized reading of arbitrary entity data, including sensitive credential tables such as jhi_user.

References

Community reviews

Loading reviews…