Skip to content
Mobile

CVE-2026-9222

9.2
Critical
EPSS 0.41%Jun 26, 2026

Hash-only auth enables full backend access.

common questions

Is CVE-2026-9222 being exploited?

Not confirmed. CVE-2026-9222 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-9222?

CVE-2026-9222 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-9222?

Not known from our data. No patch reference has been recorded for CVE-2026-9222, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-9222 affect?

CVE-2026-9222 affects Setracker2 Android Companion App (com.tgelec.setracker) <= v3.1.5. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-9222?

Update to patched version; re-auth sessions after upgrade.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Setracker2 Android Companion App (com.tgelec.setracker) <= v3.1.5
impact

Attacker with a password hash can authenticate to the backend and gain full control.

action required

Patch when possible

affected versions
Shenzhen i365-Tech Co. Ltd. Setracker2 Parental Control App (Android) package com.tgelec.setracker
  • affected<= 3.1.5
  • affected3.4.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free