Quick answers
- Is CVE-2026-54376 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54376 being exploited in the wild.
- How severe is CVE-2026-54376?
- High severity, with a CVSS score of 8.2, published 4 November 2026.
- Which products and versions are affected?
- Shenzhen Shine Industrial VitaFit Android before 2.8.1.0.
- Is there a fix for CVE-2026-54376?
- Yes: fixed in VitaFit 2.8.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54376 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-54376?
- Check whether you run Shenzhen Shine Industrial VitaFit Android at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: VitaFit 2.8.1.0
Technical details
The vulnerability is an insecure custom URI scheme (vitafit://vtio.cn) used for OAuth callback handling in the Fitbit integration. A malicious application can register the same URI scheme to intercept the 30-day Fitbit authorization token containing weight scope delivered in the callback URL, gaining access to the victim's Fitbit Body API. This is a local attack requiring the user to trigger the Fitbit login flow while the malicious app is installed, but no elevated privileges are needed.
Affected products
- Shenzhen Shine Industrial VitaFit Android before 2.8.1.0
Timeline
- 2026-11-04: disclosed
- 2026-11-03: patched: VitaFit 2.8.1.0 released