ZTE patched four vulnerabilities in its SmartLife mobile app and cloud-account backend that could enable fraudulent registration, email and account enumeration, server-information exposure, and takeover of connected-home accounts. The most severe issue, CVE-2026-86553 (CVSS 8.8), allowed a password-reset request containing a target backend account ID and a new password to succeed without validating a reset code, prior password, or other proof that the requester controlled the account.
Attackers could pair the reset flaw with CVE-2026-86554, which revealed whether an email address was registered and returned its associated backend account ID, creating a path from a known email address to a valid authenticated session. The reported proof of concept used researcher-controlled accounts and confirmed that the original password was invalidated after reset. ZTE assigned CVE-2026-86552 through CVE-2026-86555, confirmed patches for all four issues, and advised users to update SmartLife and review account passwords, connected devices, and shared-home permissions.

See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
ZTE remediated CVE-2026-86552 through CVE-2026-86555, including CVE-2026-86553, an unverified password-reset flaw, and CVE-2026-86554, an email and backend account-ID disclosure issue. ZTE issued advisories for the four vulnerabilities on this date.
Researcher Mina Nageh Salama identified four vulnerabilities in ZTE SmartLife and its cloud-account services, including an account-takeover chain that combined email/account-ID disclosure with an unverified password reset. The password-reset behavior was validated only using researcher-controlled accounts, where the replacement password successfully authenticated and the previous password no longer worked.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cryptika.com
Open sourcecybersecuritynews.com
Open sourcereddit.com
Open sourceminanagehsalalma.github.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.