# CVE-2026-54372: VitaFit Android < 2.8.1.0 Insecure TLS Certificate Validation

Status: published. Published: 2026-11-04. Updated: 2026-11-04.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Shenzhen Shine Industrial Co., Ltd. / VitaFit: ≥ 0; < 2.8.1.0 (affected, custom). Source: CNA: VulnCheck

## Severity and prioritization

- CVSS 4.0: 8.7 (high); 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; source: CNA: VulnCheck

- CVSS 3.1: 8.8 (high); CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; source: CNA: VulnCheck

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-295

## Exploit evidence

- exploit: https://github.com/je-lv/vitafit-security-research (CNA: VulnCheck)

## References

- https://github.com/je-lv/vitafit-security-research (CNA: VulnCheck; technical-description, exploit)

- https://play.google.com/store/apps/details?id=com.vt.vitafit (CNA: VulnCheck; product)

- https://www.vulncheck.com/advisories/vitafit-android-insecure-tls-certificate-validation (CNA: VulnCheck; third-party-advisory)

## Provenance

- CNA: VulnCheck: https://www.cve.org/CVERecord?id=CVE-2026-54372; retrieved 2026-11-04; source updated 2026-11-04

Revision: 1740ac61845e6bcdc00350ae6c3da7cc2e8aa3e4b31b1ca5627ffbd4b0b2d701

Canonical: https://y2.dev/cve/CVE-2026-54372

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.