Skip to main content
VulnerabilityPublished

CVE-2026-82042: UTMStack before 11.2.16 contains an authentication bypass vulnerability that allows remote attackers to gain full administrative API access by

Affects UTMStackSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.8 Critical : upgrade to 11.2.16 as a priority.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% 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:N/UI:N/S:U/C:H/I:H/A:H

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

A fix is available in UTMStack version 11.2.16. Users should upgrade to version 11.2.16 or later to remediate this vulnerability. No other mitigation guidance is provided in the input data.

Description

UTMStack versions before 11.2.16 have an authentication bypass vulnerability (CVE-2026-82042) that allows remote attackers to gain full administrative API access by using a valid Utm-Internal-Key header matching the INTERNAL_KEY environment variable. This bypass does not require a user account or JWT and lacks path restrictions, constant-time comparison, rate limiting, or audit logging. Exploitation enables attackers to create accounts, manage users, exfiltrate data, and modify security rules.

References

Community reviews

Loading reviews…