# CVE-2026-82043: UTMStack < 11.2.16 Account Enumeration via Password Reset Endpoint

> Unauthenticated attackers can enumerate registered email addresses via differing HTTP responses in the password reset endpoint, facilitating targeted phishing.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-62x9-x97p-5mj3

## What is CVE-2026-82043?

CVE-2026-82043 is a medium-severity vulnerability in UTMStack, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UTMStack before 11.2.16 contains an account enumeration vulnerability that allows unauthenticated attackers to determine registered email addresses by observing differing HTTP responses from the POST /api/account/reset-password/init endpoint. Attackers can submit arbitrary email addresses and distinguish registered accounts, which return 200 OK, from unregistered accounts, which trigger a 500 Internal Server Error with backend error details, enabling targeted phishing or credential attacks.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2026-82043?


## How do I fix CVE-2026-82043?

No fix has been published for CVE-2026-82043 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82043 being exploited?

There is no known exploitation of CVE-2026-82043 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82043 and fix it if it is affected.

What it is: CVE-2026-82043 is a medium-severity vulnerability in UTMStack, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82043 in the wild and no public exploit code.

Affected product: UTMStack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82043/ (Markdown: https://insights.sbomify.com/CVE-2026-82043/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82043
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82043
- OSV: https://osv.dev/vulnerability/CVE-2026-82043

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82043/
Summaries are generated and may contain mistakes; the official description above is the record.