CVE-2026-9222

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-26. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
15.3%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-9222(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 33× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 00:20 UTCEG score recompute
  2. 2026-07-07 00:20 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 11:10 UTCEG score recompute
  5. 2026-07-06 11:10 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 21:37 UTCEG score recompute
  8. 2026-07-05 21:37 UTCGHSA enrichment
  9. 2026-07-05 08:28 UTCEG score recompute
  10. 2026-07-05 08:28 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-04 19:20 UTCEG score recompute
  13. 2026-07-04 19:19 UTCGHSA enrichment
  14. 2026-07-04 06:31 UTCEPSS rescore
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:10 UTCEG score recompute
  17. 2026-07-04 06:10 UTCGHSA enrichment
  18. 2026-07-03 16:58 UTCEG score recompute
  19. 2026-07-03 16:58 UTCGHSA enrichment
  20. 2026-07-03 03:49 UTCEG score recompute
  21. 2026-07-03 03:49 UTCGHSA enrichment
  22. 2026-07-02 14:41 UTCEG score recompute
  23. 2026-07-02 14:40 UTCGHSA enrichment
  24. 2026-07-02 01:32 UTCEG score recompute
  25. 2026-07-02 01:32 UTCGHSA enrichment
Show 29 more
  1. 2026-07-01 15:07 UTCEPSS rescore
  2. 2026-07-01 12:22 UTCEG score recompute
  3. 2026-07-01 12:22 UTCGHSA enrichment
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 23:13 UTCEG score recompute
  6. 2026-06-30 23:13 UTCGHSA enrichment
  7. 2026-06-30 10:03 UTCEG score recompute
  8. 2026-06-30 10:03 UTCGHSA enrichment
  9. 2026-06-29 20:52 UTCEG score recompute
  10. 2026-06-29 20:52 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 07:43 UTCEG score recompute
  13. 2026-06-29 07:43 UTCGHSA enrichment
  14. 2026-06-28 18:34 UTCEG score recompute
  15. 2026-06-28 18:34 UTCGHSA enrichment
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 05:25 UTCEG score recompute
  18. 2026-06-28 05:25 UTCGHSA enrichment
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 16:16 UTCEG score recompute
  21. 2026-06-27 16:16 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-27 03:06 UTCEG score recompute
  24. 2026-06-27 03:06 UTCGHSA enrichment
  25. 2026-06-26 13:57 UTCEG score recompute
  26. 2026-06-26 13:57 UTCGHSA enrichment
  27. 2026-06-26 13:40 UTCNVD updateCVSS v4 → 9.2 · severity → HIGH
  28. 2026-06-26 00:47 UTCEG score recompute
  29. 2026-06-26 00:47 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-9222?
CVE-2026-9222 is a high vulnerability published on June 26, 2026. 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.
When was CVE-2026-9222 disclosed?
CVE-2026-9222 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9222 actively exploited?
CVE-2026-9222 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9222?
CVE-2026-9222 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-9222?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9222, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9222

Explore →

Is Your Infrastructure Affected by CVE-2026-9222?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.