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-82043 Overview
UTMStack versions before 11.2.16 contain an account enumeration vulnerability in the password reset functionality. The POST /api/account/reset-password/init endpoint returns different HTTP responses depending on whether a submitted email address exists in the system. Registered accounts return 200 OK, while unregistered addresses trigger a 500 Internal Server Error that includes backend error details. Unauthenticated attackers can abuse this behavior to enumerate valid user accounts without any credentials. The enumerated accounts can then be used for targeted phishing campaigns or credential-based attacks against the identified users. This issue is tracked as CWE-204: Observable Response Discrepancy.
Critical Impact
Unauthenticated attackers can harvest valid user email addresses from UTMStack deployments, enabling targeted phishing and credential-stuffing attacks against identified accounts.
Affected Products
- UTMStack versions prior to 11.2.16
- UTMStack backend IdentityProviderService component
- UTMStack account management API (/api/account/reset-password/init endpoint)
Discovery Timeline
- 2026-10-02 - CVE-2026-82043 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-82043
Vulnerability Analysis
The vulnerability resides in UTMStack's password reset initialization flow. When a client submits a POST /api/account/reset-password/init request with an arbitrary email address, the backend responds in a way that discloses whether the account exists. Submitting a known email returns 200 OK, indicating success. Submitting an unknown email causes the backend to raise an unhandled exception, returning 500 Internal Server Error along with backend error details.
This response-based oracle allows an unauthenticated attacker on the network to iterate through candidate email lists and reliably separate registered users from non-registered ones. Enumerated identities feed downstream attacks including spearphishing, password spraying, and credential stuffing against the UTMStack console or other services where the user may reuse credentials.
Root Cause
The root cause is improper error handling in the password reset flow combined with observable response discrepancies. The endpoint fails to normalize its response for both existing and non-existing accounts. Instead of returning a uniform generic acknowledgment, it leaks state information through differing HTTP status codes and verbose server error payloads. This is a classic [CWE-204] observable response discrepancy weakness.
Attack Vector
The attack vector is network-based and requires no authentication or user interaction. An attacker scripts repeated requests to the password reset endpoint with candidate email addresses and classifies responses by status code. Any difference between the registered and unregistered response, status code, body length, or error contents acts as a reliable oracle.
// Patch from backend/src/main/java/com/park/utmstack/service/idp_provider/IdentityProviderService.java
// Fix commit: 4e7a727 — "fix(security): patch 7 disclosed CVEs (82039-82045)"
import java.io.IOException;
import java.net.HttpURLConnection;
import java.net.InetAddress;
import java.net.MalformedURLException;
import java.net.UnknownHostException;
import java.net.URL;
import java.time.LocalDateTime;
import java.util.Optional;
import java.util.Set;
@Service
@RequiredArgsConstructor
Source: GitHub Commit 4e7a727. The patch, bundled with fixes for six other disclosed CVEs, hardens the identity provider service and related components to prevent response-based information disclosure.
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 AttacksDetection Methods for CVE-2026-82043
Indicators of Compromise
- Repeated POST requests to /api/account/reset-password/init from a single source IP within a short time window
- High volume of 500 Internal Server Error responses from the reset endpoint, indicating enumeration of non-existent accounts
- Requests to the reset endpoint containing sequentially generated, dictionary-based, or breach-list email addresses
- Absence of corresponding user-driven activity (no legitimate UI navigation prior to reset attempts)
Detection Strategies
- Create web application firewall (WAF) rules to rate-limit requests to /api/account/reset-password/init per source IP
- Alert on anomalous ratios of 500 responses to 200 responses from the reset endpoint over sliding time windows
- Correlate reset-endpoint traffic with reputation feeds to flag requests originating from known scanning infrastructure or TOR exit nodes
Monitoring Recommendations
- Enable detailed access logging on the UTMStack reverse proxy and ingest logs into a SIEM for behavioral baselining
- Track per-IP and per-ASN request rates to the account API family and alert when thresholds are exceeded
- Monitor backend application logs for unhandled exceptions originating from IdentityProviderService and related account-management services
How to Mitigate CVE-2026-82043
Immediate Actions Required
- Upgrade UTMStack to version 11.2.16 or later, which contains the fix delivered in commit 4e7a727
- Place the UTMStack console behind a reverse proxy or WAF that enforces strict rate limiting on /api/account/* endpoints
- Review authentication logs for signs of post-enumeration credential-stuffing or phishing follow-up activity
Patch Information
The fix is included in UTMStack release v11.2.16 and committed in 4e7a727. The same release addresses six additional disclosed CVEs (CVE-2026-82039 through CVE-2026-82045). Administrators should treat the full patch set as a single required upgrade. Additional context is available in the VulnCheck advisory for the account enumeration issue.
Workarounds
- Restrict network access to the UTMStack management interface to trusted administrative subnets and VPN users only
- Enforce IP-based rate limits (for example, 5 requests per minute per source) on the password reset endpoint at the proxy layer
- Deploy a WAF rule that normalizes outbound responses from the reset endpoint to a uniform 200 OK and strips verbose error bodies
- Require multi-factor authentication (MFA) for all UTMStack accounts to blunt the impact of successful enumeration
# Example NGINX configuration: rate-limit the reset endpoint and suppress verbose errors
http {
limit_req_zone $binary_remote_addr zone=reset_zone:10m rate=5r/m;
server {
location = /api/account/reset-password/init {
limit_req zone=reset_zone burst=5 nodelay;
proxy_intercept_errors on;
error_page 500 502 503 504 =200 /generic_ok.json;
proxy_pass http://utmstack_backend;
}
location = /generic_ok.json {
internal;
default_type application/json;
return 200 '{"status":"ok"}';
}
}
}
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

