CVE-2026-82045
Received Received - Intake

UTMStack JPQL Injection Vulnerability Before 11.2.16

Publication date: 2026-10-02

Last updated on: 2026-10-02

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-02
Last Modified
2026-10-02
Generated
2026-10-03
AI Q&A
2026-10-03
EPSS Evaluated
N/A
NVD
CVE-2026-82045
EUVD
EUVD-2026-91801

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
utmstack utmstack to 11.2.16 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

UTMStack before version 11.2.16 has a JPQL injection vulnerability. This flaw allows authenticated attackers to read arbitrary data by manipulating the UtmNetworkScanService.searchPropertyValues() function. The issue occurs because the function builds a JPQL query using String.format() and executes it via em.createQuery() without proper parameter binding. Attackers can inject malicious JPQL through the value parameter in the GET /api/utm-network-scans/searchPropertyValues endpoint to extract sensitive information, including credential tables like jhi_user.

Detection Guidance

To detect this vulnerability, check if your UTMStack version is before 11.2.16. Inspect logs for suspicious GET requests to /api/utm-network-scans/searchPropertyValues with JPQL injection patterns in the value parameter. Monitor for unusual data access or extraction from credential tables like jhi_user.

Impact Analysis

This vulnerability can allow attackers to read sensitive data, including user credentials, if they have authenticated access. Attackers could extract information from databases, potentially leading to unauthorized access to systems or data breaches. The impact depends on the data stored in the affected system and the attacker's goals.

Compliance Impact

This vulnerability could lead to non-compliance with regulations like GDPR or HIPAA if it results in unauthorized access to personal or sensitive health data. GDPR requires protecting personal data, and HIPAA mandates safeguarding health information. A breach could result in legal penalties, fines, or reputational damage for organizations.

Mitigation Strategies

Immediately upgrade UTMStack to version 11.2.16 or later. If upgrading is not possible, restrict access to the /api/utm-network-scans/searchPropertyValues endpoint and review all authentication credentials for potential compromise. Disable unnecessary network scans until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82045. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart