CVE-2026-86555: ZTE SmartLife hardcoded encryption key in account credentials

CVE-2026-86555 · Severity: medium · CVSS 6.2 · Published 2026-09-20

The ZTE SmartLife application stores a hardcoded encryption key in its source code that is used to protect account server information. An attacker who obtains this key can decrypt the server credentials, potentially gaining unauthorized access to backend systems and user account data.

Technologies: Zte SmartLife. Vendors: Zte.

Quick answers

Is CVE-2026-86555 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-86555 being exploited in the wild.
How severe is CVE-2026-86555?
Medium severity, with a CVSS score of 6.2, published 20 September 2026.
Which products and versions are affected?
ZTE SmartLife.
Is there a fix for CVE-2026-86555?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-86555 attacked?
It is attacked with local access, in a network appliance.
Am I affected by CVE-2026-86555?
Check whether you run Zte SmartLife. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists due to a hardcoded cryptographic key stored in plaintext within the application code. This key is used to decrypt account server information, and exposure of the key enables decryption of sensitive credentials without authentication. The vulnerability requires the attacker to obtain access to the application code or binary to extract the key.

Affected products

  • ZTE SmartLife

Timeline

  • 2026-09-20: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.