Sources: National Vulnerability Database, CVE.org, CISA KEV, FIRST EPSS
CVE-2026-54376 Overview
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.
Critical Impact
Affected Products
- VitaFit Android application (com.vt.vitafit): see the vendor advisory for the exact affected versions
Discovery Timeline
- 2026-11-04: CVE-2026-54376 published to the National Vulnerability Database by disclosure@vulncheck.com
- 2026-11-04: last updated in the NVD database
Technical Details for CVE-2026-54376
Vulnerability Analysis
CVE-2026-54376 is a Security Vulnerability weakness (CWE-926) in VitaFit Android application (com.vt.vitafit). Based on its CVSS vector, the flaw needs local or adjacent access, needs no login, and relies on a user taking an action.
With a CVSS base score of 8.2, apply the vendor fix and confirm exposure on internet facing and business critical assets first.
Root Cause
The vendor description states: 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.
Attack Vector
Based on the CVSS vector, the flaw needs local or adjacent access, needs no login, and relies on a user taking an action. Attack complexity is low complexity.
No exploitation in the wild is confirmed by CISA at the time of the last update. Check the references below for any vendor or researcher proof of concept.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Detection Methods for CVE-2026-54376
Detection Strategies
- Inventory every instance of VitaFit Android application (com.vt.vitafit) and compare the running version with the affected range above.
- Check external attack surface scans for internet facing instances of the component.
- Run an authenticated vulnerability scan once your scanner ships a check for this CVE.
Monitoring Recommendations
- Forward VitaFit Android application (com.vt.vitafit) application, access and audit logs to your SIEM for retrospective hunting.
- Alert on new processes, configuration changes or outbound connections from the affected service.
- Track the vendor advisory and the CISA KEV catalog for changes in exploitation status.
How to Mitigate CVE-2026-54376
Immediate Actions Required
- Apply the fixed version of VitaFit Android application (com.vt.vitafit) named in the vendor advisory.
- Prioritize internet facing and business critical instances first.
- Rescan after the change to confirm the exposure is closed.
Patch Information
Use the fixed version listed in the vendor advisory for VitaFit Android application (com.vt.vitafit).
Workarounds
- If patching must wait, restrict network access to the affected service and place it behind authentication or a web application firewall rule.
CWE References
Technical References
This entry is built directly from NVD, CISA KEV and EPSS data. Verify fixed versions in the vendor advisory before you deploy.
Frequently asked questions
Earn your free CTEM certification.
Learn to scope, prioritize, validate and mobilize fixes for CVEs like CVE-2026-54376 with a free CTEM certification.
Beginner / Practitioner / Program Leader
Explore certifications