PatchTheCVECVE-2020-13425: TrackR devices through 2020-05-06 allow attackers to trigger the Beep (aka alarm) feature, which will eventual
CVE-2020-13425 is a high-severity flaw (CVSS 7.1) affecting trackr firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
TrackR devices through 2020-05-06 allow attackers to trigger the Beep (aka alarm) feature, which will eventually cause a denial of service when battery capacity is exhausted.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.1 (High) |
| Attack vector | Adjacent network |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.6% (top 53%) |
| CISA exploited list | No |
| Weakness | CWE-862 |
| Published | 2020-05-23 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-13425?
trackr firmware: upgrade to newer than 2020-05-06. Exact commands for each OS are on this page.
Is CVE-2020-13425 being exploited?
CVE-2020-13425 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-13425 affect?
CVE-2020-13425 affects trackr firmware. Severity is high (CVSS 7.1). TrackR devices through 2020-05-06 allow attackers to trigger the Beep (aka alarm) feature, which will eventually cause a denial of service when battery capacity is exhausted.
How urgent is CVE-2020-13425?
Priority 42/100. High severity; Public exploit reference