CVE-2026-82043: UTMStack before 11.2.16 contains an account enumeration vulnerability that allows unauthenticated attackers to determine registered email addresses
Affects UTMStackSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 11.2.16 when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 16% 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:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubutmstack/UTMStackpkg:github/utmstack/UTMStackOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade UTMStack to version 11.2.16 or later where this vulnerability is fixed. If upgrading is not immediately possible, consider implementing rate limiting or generic error responses on the password reset endpoint to prevent account enumeration. Patch status is not explicitly confirmed in the input, but the version 11.2.16 is indicated as the fixed version.
Description
UTMStack versions prior to 11.2.16 have an account enumeration vulnerability. This flaw allows unauthenticated attackers to determine if an email address is registered by submitting it to the password reset initiation endpoint. Registered emails return a 200 OK response, while unregistered ones cause a 500 Internal Server Error with backend details. This behavior enables attackers to distinguish valid accounts, potentially facilitating targeted phishing or credential attacks.
References
- nvd.nist.gov/vuln/detail/CVE-2026-82043 (opens in a new tab)
- github.com/utmstack/UTMStack/commit/4e7a727c3b8d8e2ad020d3b4f982a6d085dbecdd (opens in a new tab)
- github.com/UTMStack/UTMStack/releases/tag/v11.2.16 (opens in a new tab)
- vulncheck.com/advisories/utmstack-account-enumeration-via-password-reset-endpoint (opens in a new tab)