# CVE-2026-86555: Hardcoded Key Vulnerability in ZTE SmartLife APP

> Attackers can extract a hardcoded key from the ZTE SmartLife mobile app to decrypt and expose sensitive account server information.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-6rhq-q57h-9phf

## What is CVE-2026-86555?

CVE-2026-86555 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The ZTE SmartLife application has a hardcoded key. The key used to decrypt account server information is stored in plaintext in the code. Once the key is obtained, the server information can be decrypted, thus exposing it.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2026-86555 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86555 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86555 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-86555/ (Markdown: https://insights.sbomify.com/CVE-2026-86555/index.md)
```

## Sources

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

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