# CVE-2026-9222: Setracker2 Children's Smartwatch Ecosystem Use of password hash instead of password for authentication

> An attacker knowing the password hash can authenticate to backend services and gain full access to the Setracker2 smartwatch ecosystem.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-f7c5-2gv6-7rwj

## What is CVE-2026-9222?

CVE-2026-9222 is a critical authentication bypass vulnerability in Shenzhen i365-Tech Co. Ltd. Setracker2 Parental Control App (Android) package com.tgelec.setracker, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Setracker2 Android Companion App com.tgelec.setracker versions 3.1.5 and prior only require the password hash when authenticating with backend services from the client. This could allow an attacker, who knows the hash, to authenticate and gain full access.

Weakness: CWE-836 (Use of Password Hash Instead of Password for Authentication)

## Which versions are affected by CVE-2026-9222?


## How do I fix CVE-2026-9222?

No fix has been published for CVE-2026-9222 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-9222 being exploited?

There is no known exploitation of CVE-2026-9222 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9222 and fix it if it is affected.

What it is: CVE-2026-9222 is a critical authentication bypass vulnerability in Shenzhen i365-Tech Co. Ltd. Setracker2 Parental Control App (Android) package com.tgelec.setracker, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-9222 in the wild and no public exploit code.

Affected product: Shenzhen i365-Tech Co. Ltd. Setracker2 Parental Control App (Android) package com.tgelec.setracker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9222/ (Markdown: https://insights.sbomify.com/CVE-2026-9222/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9222
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9222
- OSV: https://osv.dev/vulnerability/CVE-2026-9222

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9222/
Summaries are generated and may contain mistakes; the official description above is the record.