VitaFit Android < 2.8.1.0 Long-Lived Session Token Exposure
VitaFit Android app versions before 2.8.1.0 store session tokens in application backups. The fix is 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. Affected VitaFit Android app versions before 2.8.1.0 Session tokens are stored in application backups
- 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.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
CVE-2026-54375 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (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? →
- 14/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 apps before version 2.8.1.0 expose long-lived session tokens in application backups, which an attacker with local access can extract or intercept without logging in or any action by the user. A stolen token, valid for ten years, lets the attacker read and modify the victim's account or delete its authentication record, locking the legitimate owner out.
Read the original description
VitaFit Android application (com.vt.vitafit) before 2.8.1.0 contains an insecure session management vulnerability that allows attackers to extract or intercept unencrypted m_session_id tokens stored in application backups, which remain valid for ten years. Attackers can use a stolen session token to read and modify the victim's account or delete the account's authentication record, preventing the legitimate owner from logging in again.
What to do
Check whether your setup matches what the bug needs.
Affected VitaFit Android app versions before 2.8.1.0 Session tokens are stored in application backupsUpgrade 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-54375
Is CVE-2026-54375 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?
Session tokens, which keep a logged-in session open, are stored in the app's backups. A stolen token can be used to read and change the victim's account, or to delete the account's authentication record so the owner cannot log in again.Source: vulncheck.com
Which versions are affected by CVE-2026-54375?
VitaFit: before 2.8.1.0.Source: cve.now feed data
Am I affected, and how do I check?
The VitaFit Android app (package com.vt.vitafit) is affected in versions before 2.8.1.0. To check an installed copy, look up the version in the app's details under Android Settings > Apps, or in the app's own about screen.Source: vulncheck.com
How do I fix CVE-2026-54375?
Update the VitaFit Android app to version 2.8.1.0 or later.Source: vulncheck.com