Summary
CVE-2026-82042 is a critical authentication bypass vulnerability in UTMStack, an open-source SIEM/unified threat management platform. The flaw resides in the InternalApiKeyFilter component, which accepts any request carrying a valid Utm-Internal-Key header matching the server’s INTERNAL_KEY environment variable as fully authenticated, granting the requester administrative API access without a user account or JWT. It affects all UTMStack versions prior to 11.2.16 and carries a CVSS score of 9.3 (also reported as 9.8 under CVSS v3.1).
Technical details
- Root cause:
InternalApiKeyFiltervalidates requests solely by comparing theUtm-Internal-KeyHTTP header against theINTERNAL_KEYenvironment variable, with no path restriction limiting which endpoints accept this header, no role or context check tying the key to a specific internal caller, and no rate limiting or audit logging around key validation attempts. - Trigger conditions: An attacker who obtains the value of
INTERNAL_KEY(e.g., through source code exposure, leaked configuration files, or memory/process disclosure) can send it in theUtm-Internal-Keyheader on any API request. - Attack vector: Network-based; no authentication, user interaction, or special privileges are required beyond knowledge of the internal key value.
- Impact: Full administrative API access — creation and management of user accounts, exfiltration of sensitive data, and modification of security configurations (e.g., intrusion prevention settings, firewall rules, traffic routing), enabling further lateral movement within the protected network.
Affected software
- UTMStack versions prior to 11.2.16 (all versions from the product’s initial release up to 11.2.16).
Severity
- CVSS v3.1: 9.8 (Critical) —
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - CVSS v4.0: 9.3 (Critical)
Mitigation and recommended actions
- Immediate: Upgrade UTMStack to version 11.2.16 or later, which fixes the
InternalApiKeyFilterauthentication logic. - Additional precaution: Rotate the
INTERNAL_KEYenvironment variable value after upgrading, in case the prior key value was exposed. - If immediate patching is not possible: Restrict network access to the UTMStack management API to trusted internal networks only, and audit for any configuration or source exposure that could leak the
INTERNAL_KEYvalue.

