VitaFit Android < 2.8.1.0 Custom URI Scheme Token Hijacking
VitaFit Android versions before 2.8.1.0 use a custom URI scheme that a malicious app on the same device can also register, letting it capture a Fitbit authorization token. Fixed in 2.8.1.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.1.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. VitaFit Android application (com.vt.vitafit) versions before 2.8.1.0 A malicious application on the device registers the same callback scheme (vitafit://vtio.cn)
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
CVE-2026-54376 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects VitaFit; fixed in 2.8.1.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 13/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.8.1.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
VitaFit Android versions before 2.8.1.0 contain a flaw in their custom URI scheme that lets a malicious app on the same device intercept Fitbit login tokens during sign-in. Exploitation requires local access to the device and a user action, and an attacker who gets the token could read, create, and delete the victim's weight and body-fat records through the Fitbit Body API.
Read the original description
VitaFit Android application (com.vt.vitafit) before 2.8.1.0 contains an insecure custom URI scheme vulnerability that allows a malicious application to intercept Fitbit login tokens by registering the same callback scheme (vitafit://vtio.cn). Attackers can capture the 30-day Fitbit authorization token with weight scope delivered in the callback URL to read, create, and delete the victim's weight and body-fat records via the Fitbit Body API.
What to do
Check whether your setup matches what the bug needs.
VitaFit Android application (com.vt.vitafit) versions before 2.8.1.0 A malicious application on the device registers the same callback scheme (vitafit://vtio.cn)Upgrade to a fixed version: 2.8.1.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Shenzhen Shine Industrial Co., Ltd. VitaFit
fixed in 2.8.1.0
Evidence 3
- Exploit
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54376
Is CVE-2026-54376 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A malicious app installed on the same Android device can register the same callback scheme (vitafit://vtio.cn) as VitaFit. This lets it capture the 30-day Fitbit authorization token with weight scope. With that token, it can read, create, and delete the victim's weight and body-fat records through the Fitbit Body API.Source: vulncheck.com
Which versions are affected by CVE-2026-54376?
VitaFit: before 2.8.1.0.Source: cve.now feed data
Am I affected, and how do I check?
The VitaFit Android application (com.vt.vitafit) is affected in versions before 2.8.1.0. To check a device, look up the installed version of com.vt.vitafit in Android's app details.Source: vulncheck.com
How do I fix CVE-2026-54376?
Update the VitaFit Android application to version 2.8.1.0 or later, which fixes the issue.Source: vulncheck.com