CVE-2026-9221

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

The Setracker2 Android Companion App (com.tgelec.setracker) versions 3.1.5 and earlier uses MD5 to generate a request signature for authenticating communications between the mobile client and the backend REST API. Attackers could potentially reverse the signature to recover the session ID. With the session ID exposed, an attacker could impersonate the legitimate user and issue authenticated API requests.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.6%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic
https://raw.githubusercontent.com/cisagov/CSAF/refs/heads/develop/csaf_files/VA/white/2026/va-26-176-01.json

Vendor Advisories for CVE-2026-9221(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 10× in last 7d / 80× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:23 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 17:08 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-17 04:54 UTCGHSA enrichment
  12. 2026-07-16 17:52 UTCGHSA enrichment
  13. 2026-07-16 17:03 UTCEPSS rescore
  14. 2026-07-16 06:51 UTCGHSA enrichment
  15. 2026-07-15 19:27 UTCGHSA enrichment
  16. 2026-07-15 16:57 UTCEPSS rescore
  17. 2026-07-15 08:25 UTCGHSA enrichment
  18. 2026-07-15 02:00 UTCEPSS rescore
  19. 2026-07-14 21:22 UTCGHSA enrichment
  20. 2026-07-14 10:21 UTCGHSA enrichment
  21. 2026-07-13 23:19 UTCGHSA enrichment
  22. 2026-07-13 22:31 UTCEPSS rescore
  23. 2026-07-13 12:17 UTCGHSA enrichment
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-13 01:15 UTCGHSA enrichment
Show 55 more
  1. 2026-07-12 14:13 UTCGHSA enrichment
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-12 02:56 UTCGHSA enrichment
  4. 2026-07-11 15:55 UTCGHSA enrichment
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 04:54 UTCGHSA enrichment
  7. 2026-07-10 17:52 UTCGHSA enrichment
  8. 2026-07-10 06:50 UTCGHSA enrichment
  9. 2026-07-09 19:47 UTCGHSA enrichment
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 08:45 UTCGHSA enrichment
  12. 2026-07-08 21:42 UTCGHSA enrichment
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 10:41 UTCGHSA enrichment
  15. 2026-07-07 23:39 UTCGHSA enrichment
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 12:37 UTCGHSA enrichment
  18. 2026-07-07 01:35 UTCGHSA enrichment
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 14:32 UTCGHSA enrichment
  21. 2026-07-06 03:31 UTCGHSA enrichment
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-05 16:30 UTCGHSA enrichment
  24. 2026-07-05 05:24 UTCGHSA enrichment
  25. 2026-07-05 02:31 UTCEPSS rescore
  26. 2026-07-04 18:23 UTCGHSA enrichment
  27. 2026-07-04 07:18 UTCGHSA enrichment
  28. 2026-07-04 06:31 UTCEPSS rescore
  29. 2026-07-04 06:31 UTCEPSS rescore
  30. 2026-07-03 20:13 UTCGHSA enrichment
  31. 2026-07-03 09:12 UTCGHSA enrichment
  32. 2026-07-02 22:11 UTCGHSA enrichment
  33. 2026-07-02 11:10 UTCGHSA enrichment
  34. 2026-07-02 00:09 UTCGHSA enrichment
  35. 2026-07-01 15:07 UTCEPSS rescore
  36. 2026-07-01 13:08 UTCGHSA enrichment
  37. 2026-07-01 02:07 UTCGHSA enrichment
  38. 2026-06-30 23:22 UTCEPSS rescore
  39. 2026-06-30 15:04 UTCGHSA enrichment
  40. 2026-06-30 04:01 UTCGHSA enrichment
  41. 2026-06-29 17:00 UTCGHSA enrichment
  42. 2026-06-29 14:06 UTCEPSS rescore
  43. 2026-06-29 05:58 UTCGHSA enrichment
  44. 2026-06-28 18:56 UTCGHSA enrichment
  45. 2026-06-28 14:07 UTCEPSS rescore
  46. 2026-06-28 07:54 UTCGHSA enrichment
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-27 20:53 UTCGHSA enrichment
  49. 2026-06-27 09:52 UTCGHSA enrichment
  50. 2026-06-27 03:08 UTCEPSS rescore
  51. 2026-06-26 22:49 UTCGHSA enrichment
  52. 2026-06-26 13:40 UTCNVD updateCVSS v4 → 8.7
  53. 2026-06-26 11:48 UTCGHSA enrichment
  54. 2026-06-26 00:47 UTCEG score recompute
  55. 2026-06-26 00:47 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-9221?
CVE-2026-9221 is a high vulnerability published on June 26, 2026. The Setracker2 Android Companion App (com.tgelec.setracker) versions 3.1.5 and earlier uses MD5 to generate a request signature for authenticating communications between the mobile client and the backend REST API. Attackers could potentially reverse the signature to recover the session ID. With the…
When was CVE-2026-9221 disclosed?
CVE-2026-9221 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9221 actively exploited?
CVE-2026-9221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9221?
CVE-2026-9221 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-9221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9221, 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-9221

Explore →

Is Your Infrastructure Affected by CVE-2026-9221?

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

Start Free Scan →Browse All CVEs