Loading vulnerability…
CVE-2026-86555 is a hardcoded cryptographic key vulnerability in the ZTE SmartLife mobile application. A key used to decrypt account-server information is embedded in plaintext within application code, allowing it to be recovered through application analysis and used to decrypt the protected information.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CVSS 6.2 hardcoded-key vulnerability in the ZTE SmartLife application that permits extraction of an embedded key and decryption of sensitive account-server information.
A hardcoded mobile-application key vulnerability in ZTE SmartLife that could allow extraction of the key and decryption of sensitive account-server information.
One of four reported ZTE SmartLife vulnerabilities. The provided content does not specify its technical root cause or impact.
A hardcoded plaintext decryption key in the ZTE SmartLife application can be extracted from the code and used to decrypt account-server information, exposing that server information.
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.