VitaFit Android < 2.8.1.0 Insecure TLS Certificate Validation
The VitaFit Android app (com.vt.vitafit) before 2.8.1.0 trusts all TLS certificates and accepts any hostname. 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
- Not reported
Do first: Upgrade to a fixed version: 2.8.1.0.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure?/25Exposure: unknown (data gap). Advisories don't say whether default setups are affected
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- 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 31 if advisories confirm default setups are exposed
CVE-2026-54372 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (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? →
- 9/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? →
- Unclear
- 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's Android app (com.vt.vitafit) before 2.8.1.0 does not properly validate TLS certificates, so an attacker on the same network segment, without logging in or any user action, can intercept and modify HTTPS traffic to capture account sessions and health-related data and use a captured session to delete the account's authentication record and block legitimate logins.
Read the original description
VitaFit Android application (com.vt.vitafit) before 2.8.1.0 contains an insecure TLS/SSL certificate validation vulnerability that allows network-based attackers to intercept and modify HTTPS traffic by exploiting a custom X509TrustManager that trusts all certificates and a hostname verifier that accepts any hostname. Attackers can perform a man-in-the-middle attack to capture account sessions and health-related API data, and use a captured session to delete the account's authentication record and prevent legitimate login.
What to do
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-54372
Is CVE-2026-54372 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?
The app's HTTPS certificate checks are effectively disabled, so it accepts any certificate and any hostname. This lets an attacker positioned between the app and the server intercept and modify traffic, capturing account sessions and health-related API data.Source: vulncheck.com
Which versions are affected by CVE-2026-54372?
VitaFit: before 2.8.1.0.Source: cve.now feed data
Am I affected, and how do I check?
VitaFit Android app com.vt.vitafit versions before 2.8.1.0 are affected. To check, compare the installed version of com.vt.vitafit in Android's app details with 2.8.1.0.Source: vulncheck.com
How do I fix CVE-2026-54372?
Update the VitaFit Android app to version 2.8.1.0 or later.Source: vulncheck.com