CVE-2026-86554

Email enumeration and account ID leakage vulnerabilities in ZTE SmartLife APP

Published Sep 20, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
SmartLife app dynamically generates brand‑new SmartLife application authentication parameters within its runtime process. With the obtained SmartLife application authentication parameters, attackers can directly invoke the backend interface /account/verify.serv to determine whether a target email address is registered for a SmartLife account. If the account exists, the real backend account ID can also be retrieved.

Analysis

AI-generated

Technical impact

SmartLife app creates new authentication parameters during execution. An attacker exploiting these parameters can call the backend /account/verify.serv endpoint to discover whether an email address is registered on the service. If the address is valid, the actual backend account identifier is returned, exposing sensitive user information. This vulnerability allows an attacker to gather a list of valid user accounts and obtain account IDs for further exploitation attempts. The weakness is related to improper authorization of verification functionality (CWE-269).

Affected Systems

The vulnerability affects the ZTE SmartLife application provided by ZTE. Specific product details are listed under ZTE:ZTESW, covering all current versions of the SmartLife mobile app where dynamic authentication parameter generation is implemented. No specific version numbers are disclosed in the advisory.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate impact. The EPSS score is not available, so exploitation probability cannot be quantified, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is an attacker sending crafted requests to the backend API from within the mobile app or via a network pass‑through, requiring only knowledge of the authentication parameters. Successful exploitation would enable enumeration of user accounts and disclosure of account identifiers, which could facilitate further targeted attacks such as phishing or credential stuffing.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest version of the ZTE SmartLife app that incorporates the vendor fix for authentication parameter handling.
  • Configure or enable backend services to enforce stricter access controls on the /account/verify.serv endpoint, rejecting enumeration attempts that do not provide proper authorization tokens.
  • Enable multi‑factor authentication for all SmartLife accounts to reduce risk if account identifiers are compromised.

Generated by OpenCVE AI on September 20, 2026 at 09:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Zte
Zte ztesw
Vendors & Products Zte
Zte ztesw
Type Values Removed Values Added
Description SmartLife app dynamically generates brand‑new SmartLife application authentication parameters within its runtime process. With the obtained SmartLife application authentication parameters, attackers can directly invoke the backend interface /account/verify.serv to determine whether a target email address is registered for a SmartLife account. If the account exists, the real backend account ID can also be retrieved.
Title Email enumeration and account ID leakage vulnerabilities in ZTE SmartLife APP
Weaknesses CWE-269
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-269

    Improper Privilege Management

Sources

Status
PUBLISHED
Assigner
zte
Published
Updated
Sep 21, 2026, 6:07 PM
Reserved
Sep 8, 2026, 2:55 AM
Status
Deferred
Published
Sep 20, 2026, 8:16 AM
Modified
Sep 22, 2026, 7:41 PM