# CVE-2026-86554: Email enumeration and account ID leakage vulnerabilities in ZTE SmartLife APP

> Attackers can enumerate registered emails and retrieve account IDs via backend interfaces, potentially facilitating account takeover.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-72pp-r64r-349h

## What is CVE-2026-86554?

CVE-2026-86554 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-86554 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86554 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86554 in the wild and no public exploit code.

Affected product: ZTE SmartLife. 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-86554/ (Markdown: https://insights.sbomify.com/CVE-2026-86554/index.md)
```

## Sources

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

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