{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-86552 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-86552 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-86552 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-86552 and fix it if it is affected.\n\nWhat it is: CVE-2026-86552 is a medium-severity vulnerability in ZTE SmartLife, published on 20 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-86552 in the wild and no public exploit code.\n\nAffected product: ZTE SmartLife. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-86552/ (Markdown: https://insights.sbomify.com/CVE-2026-86552/index.md)","id":"CVE-2026-86552","markdown":"https://insights.sbomify.com/CVE-2026-86552/index.md","name":"CVE-2026-86552","record":{"aliases":["GHSA-5vgr-9q5r-pvpj"],"analysis":null,"analysis_generated_by":null,"assigner":"zte","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"SmartLife app dynamically generates brand‑new SmartLife application authentication parameters at runtime. With the acquired SmartLife application authentication credentials, an attacker can directly complete registration using any arbitrary email address via the backend interface /account/person/signup.serv. Email ownership is not verified prior to registration.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-09-20","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-09-20T19:12:28Z","kind":"github_poc","ref":"https://github.com/minanagehsalalma/zte-smartlife-app-pwned","stars":0,"title":"ZTE SmartLife security findings leading to account takeover: 100K+ Google Play downloads and CVE-2026-86552 through CVE-2026-86555."}],"tier":"poc_unverified"},"has_fix":null,"headline":"A vulnerability that skips email ownership verification for account registration in ZTE SmartLife APP","id":"CVE-2026-86552","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"A password reset vulnerability in ZTE SmartLife APP","id":"CVE-2026-86553"},"packages":[],"prev":{"headline":"Wi-Fi MAC Address Obtainment by Non-privileged Program Vulnerability in ZTE Z80Ultra (NX741J) product","id":"CVE-2026-86551"},"products":["SmartLife"],"published":"2026-09-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["ZTE"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-86552/"}