# CVE-2026-9219: Setracker2 Children's Smartwatch Ecosystem Generation of Predictable Numbers or Identifiers

> Attackers can predict registration IDs to enroll other users' smartwatches, bypassing authentication in the Setracker2 Android companion app.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/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-jpv7-7g7j-hgwr

## What is CVE-2026-9219?

CVE-2026-9219 is a high-severity 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 have a predictable registration ID derived from IMEI. The enrollment system lacks additional authentication before assignment. If an attacker is able to obtain the registration ID, they would be able to arbitrarily enroll watches belonging to other users.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers)

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


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

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

## Is CVE-2026-9219 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9219 is a high-severity 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-9219 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-9219/ (Markdown: https://insights.sbomify.com/CVE-2026-9219/index.md)
```

## Sources

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

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