Skip to main content
Vulnerability Database/CVE-2026-82042

CVE-2026-82042: UTMStack Authentication Bypass Vulnerability

CVE-2026-82042 is an authentication bypass flaw in UTMStack that lets attackers gain full administrative API access using a valid internal key header. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-82042 Overview

CVE-2026-82042 is an authentication bypass vulnerability in UTMStack versions prior to 11.2.16. The InternalApiKeyFilter component accepts any request that presents a valid Utm-Internal-Key header matching the INTERNAL_KEY environment variable. The filter applies no path restriction, no constant-time comparison, no rate limiting, and no audit logging. An attacker who obtains the key value gains full administrative API access without a user account or JSON Web Token (JWT). This grants the ability to create accounts, manage users, exfiltrate data, and modify security rules. The weakness is classified as Missing Authentication for Critical Function [CWE-306].

Critical Impact

Remote, unauthenticated attackers possessing the internal key value can perform full administrative actions against UTMStack, including account creation, data exfiltration, and modification of security rules.

Affected Products

  • UTMStack versions prior to 11.2.16
  • UTMStack backend InternalApiKeyFilter component
  • Deployments exposing the UTMStack API over the network

Discovery Timeline

  • 2026-10-02 - CVE-2026-82042 published to the National Vulnerability Database (NVD)
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-82042

Vulnerability Analysis

UTMStack's backend registers an authentication filter named InternalApiKeyFilter intended for internal service-to-service traffic. The filter inspects the Utm-Internal-Key HTTP header and compares it to the value of the INTERNAL_KEY environment variable. When the header matches, the filter grants the caller full administrative authority on any endpoint it protects.

The filter does not scope matching to internal network paths, loopback traffic, or specific controllers. It performs a direct string comparison, which is not constant-time and does not emit audit log entries on success or failure. No per-source rate limiting is applied. The result is a single static secret that unlocks the entire administrative API surface over the network.

Root Cause

The root cause is Missing Authentication for Critical Function [CWE-306] combined with Broken Access Control. A shared secret used for service-to-service calls was treated as sufficient authentication for administrative actions. There is no binding of the key to a caller identity, no path allow-list, and no transport restriction. Any entity able to send a request to the UTMStack API with the correct header value is accepted as an administrator.

Attack Vector

Exploitation requires network access to the UTMStack API and knowledge of the INTERNAL_KEY value. The key can leak through container environment variables, process listings, backup archives, Git history, configuration management logs, or shared container images. Once the attacker holds the value, they issue standard HTTPS requests to any administrative endpoint and include the Utm-Internal-Key header. No user account, password, token, or multi-factor step is required. The attacker can enumerate users, create a new administrative account for persistence, read logged telemetry, and change identification or response rules.

java
// Vendor patch excerpt - commit 4e7a727
// backend/src/main/java/com/park/utmstack/service/network_scan/UtmNetworkScanService.java
// Replaces string interpolation with parameterized queries as part of the
// release that also hardens InternalApiKeyFilter in v11.2.16.
if (StringUtils.hasText(value)) {
    if (prop == PropertyFilter.PORTS)
        sb.append(" AND cast(port as string) LIKE :value");
    else if (prop == PropertyFilter.ALIVE) {
        sb.append(" AND %1$s = :value");
    } else
        sb.append(" AND lower(%1$s) LIKE :value");
}

javax.persistence.Query q = em.createQuery(query);
if (StringUtils.hasText(value)) {
    if (prop == PropertyFilter.ALIVE) {
        q.setParameter("value", Boolean.parseBoolean(value));
    } else if (prop == PropertyFilter.PORTS) {
        q.setParameter("value", "%" + value.toLowerCase() + "%");
    } else {
        q.setParameter("value", "%" + value.toLowerCase() + "%");
    }
}
// Source: https://github.com/utmstack/UTMStack/commit/4e7a727c3b8d8e2ad020d3b4f982a6d085dbecdd

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-82042

Indicators of Compromise

  • Any HTTP request to the UTMStack API containing a Utm-Internal-Key header originating from a non-loopback or non-internal source address.
  • Creation of new administrative user accounts in UTMStack with no corresponding interactive login or audit trail.
  • Unexpected modifications to identification rules, response playbooks, or integration configurations.
  • Bulk read operations against user, alert, or log endpoints with no associated JWT or session cookie.

Detection Strategies

  • Inspect reverse proxy and load balancer logs for the presence of the Utm-Internal-Key request header and alert when the source is not an approved internal service.
  • Correlate administrative API calls that lack an Authorization bearer token with subsequent user or rule changes.
  • Baseline normal callers of the InternalApiKey endpoints and flag deviations in source IP, user agent, or request rate.

Monitoring Recommendations

  • Enable verbose access logging on the UTMStack ingress and forward logs to a centralized analytics platform for retention and query.
  • Monitor environment variable exposure in container registries, Git repositories, and CI/CD logs to detect leakage of the INTERNAL_KEY value.
  • Alert on administrative account creation, role changes, and rule modifications in near real time.

How to Mitigate CVE-2026-82042

Immediate Actions Required

  • Upgrade UTMStack to version 11.2.16 or later without delay.
  • Rotate the INTERNAL_KEY environment variable value on every UTMStack deployment, including staging and backup instances.
  • Audit all administrative accounts, API tokens, and identification rules for unauthorized changes made before the upgrade.
  • Restrict network reachability of the UTMStack API to trusted management networks only.

Patch Information

The vendor addressed the issue in UTMStack v11.2.16. The fix is included in commit 4e7a727c3b8d8e2ad020d3b4f982a6d085dbecdd, which hardens the InternalApiKeyFilter along with other disclosed issues in the 82039-82045 range. See the UTMStack v11.2.16 release notes, the vendor commit, and the VulnCheck advisory for full remediation details.

Workarounds

  • Block the Utm-Internal-Key header at an upstream reverse proxy or web application firewall for all requests originating outside the internal service network.
  • Place the UTMStack API behind a network allow-list that limits access to specific management hosts and jump boxes.
  • Rotate the INTERNAL_KEY value frequently and store it in a secrets manager rather than static environment files.
bash
# Example NGINX directive to strip the Utm-Internal-Key header
# for requests arriving from untrusted sources
location /api/ {
    if ($remote_addr !~ ^(10\.|192\.168\.|127\.)) {
        proxy_set_header Utm-Internal-Key "";
    }
    proxy_pass http://utmstack_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.