# CVE-2026-86552: A vulnerability that skips email ownership verification for account registration in ZTE SmartLife APP


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-5vgr-9q5r-pvpj

## What is CVE-2026-86552?

CVE-2026-86552 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. 

### Official description

SmartLife app dynamically generates brand‑new SmartLife application authentication parameters at runtime. With the acquired SmartLife application authentication credentials, an attacker can directly complete registration using any arbitrary email address via the backend interface /account/person/signup.serv. Email ownership is not verified prior to registration.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-86552 being exploited?

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

Public exploit code:

- ZTE SmartLife security findings leading to account takeover: 100K+ Google Play downloads and CVE-2026-86552 through CVE-2026-86555. (github_poc): https://github.com/minanagehsalalma/zte-smartlife-app-pwned

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86552 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-86552 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-86552/ (Markdown: https://insights.sbomify.com/CVE-2026-86552/index.md)
```

## Sources

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

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