Loading vulnerability…
CVE-2026-86553 is a password-reset authorization flaw affecting ZTE SmartLife versions 2.8.2 and earlier. The backend password-reset workflow accepted a target backend account identifier and attacker-selected replacement password without requiring proof of account ownership, the existing password, a reset code, or a validated reset transaction. Application authentication parameters obtainable from the mobile application's runtime could be spoofed and used with account-identification functionality to associate a registered email address with its backend account identifier, enabling a full account-takeover chain.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This 18-file static write-up and PoC repository documents four patched ZTE SmartLife account-backend vulnerabilities. The main operational artifact, pocs/direct-replay/account-takeover-poc.ps1, is a PowerShell 7 API-replay PoC. It decrypts a publicly retrieved bootstrap blob with a hardcoded AES-GCM key, reconstructs application-authentication headers, queries the account-verification endpoint to enumerate an email and obtain an accountId, resets the password without a reset code or prior password, and confirms account takeover by logging in with the new password and receiving a session token. It also demonstrates arbitrary email pre-registration/account squatting. The runtime-path PowerShell probe repeats the lifecycle against the production account API and serializes requests/results, including a check for the historical tokenless deletion condition. The two Frida JavaScript scripts instrument the official Android client: one dumps decrypted UAC server/key configuration and relevant outbound headers, while the other provides RPC functions that retrieve UAC values, generate live X-Auth-Value headers, and encrypt arbitrary payloads through the app process. Remaining files are a GitHub Pages technical article, readmes, configuration, and SVG assets. The repository explicitly states that ZTE patched affected paths and rotated keys; it is nevertheless functional exploit/replay code rather than a detection-only tool.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CVSS 8.8 authentication and password-reset flaw in ZTE SmartLife versions 2.8.2 and earlier. An attacker with a target backend account ID and spoofed application authentication data could reset the victim's password without ownership verification, enabling account takeover.
A critical improper password-reset verification flaw in ZTE SmartLife that enabled account takeover. The backend accepted an account identifier and new password without requiring server-side validation that the requester controlled the account.
An account-takeover vulnerability in the ZTE SmartLife account backend that allowed an attacker with a target account ID to reset that account's password without a reset code, current password, or validated reset transaction. The described chain used account enumeration to obtain an account ID, then reset the password and authenticate as the victim.
An account-takeover vulnerability in the SmartLife app: attackers who acquire and spoof application authentication parameters can query a registered email address's account ID through the backend API and reset that account's password.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.