Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessJoin shared/adjacent network
-
DeliveryPosition as man-in-the-middle (ARP/DNS spoof)
-
ExploitPresent rogue TLS cert accepted by trust-all manager
-
ExecutionCapture session token and health API data
-
ImpactReplay session to delete auth record and lock out user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
|
| Exploitation Conditions | Exploitation requires the attacker to occupy an on-path/man-in-the-middle position on the same or an adjacent network as the victim (AV:A) - for example a shared Wi-Fi network or a controlled access point enabling ARP/DNS spoofing - while the victim uses the VitaFit Android app (com.vt.vitafit) at a version before 2.8.1.0. No special app configuration or non-default mode is needed: the insecure behavior is built into the app's default networking, where a custom X509TrustManager trusts all certificates and the hostname verifier accepts any hostname, so any presented certificate is accepted. No authentication and no user interaction are required (PR:N/UI:N). The principal limiting factors are the network-adjacency requirement (not exploitable from the open internet) and the version ceiling - updating to 2.8.1.0 or later removes the flaw. |
| Impact | The CVSS 4.0 base score of 8.7 (High) reflects full compromise of the vulnerable system's confidentiality, integrity and availability (VC:H/VI:H/VA:H), but the attack vector is Adjacent (AV:A), not Network - the attacker must sit on the same or an adjacent network path (e.g. shared Wi-Fi, a malicious access point, or a position allowing ARP/DNS spoofing) rather than attacking across the open internet, which meaningfully narrows the real-world opportunity. Attack complexity is Low and no privileges or user interaction are required (AC:L/PR:N/UI:N), so once the attacker is on-path the flaw is trivially exploitable because the app's custom X509TrustManager trusts all certificates and the hostname verifier accepts any hostname. This is not in CISA KEV and no EPSS score was supplied in the input, so there is no quantitative exploitation-probability or active-exploitation signal to weigh; a public PoC reference exists (a GitHub security-research repository) but it is not verified as working exploit code. The vuln.today decision label is this_week, consistent with a serious-but-not-emergency priority: a genuine high-impact flaw whose exploitation is gated by network adjacency rather than a mass-exploitable internet-facing issue. Net assessment: a real priority for the affected user population, but the Adjacent vector and absence of KEV/EPSS evidence argue for targeted/opportunistic local-network exploitation rather than widespread automated attacks. |
| Exploit ScenarioDerived | An attacker on the same network as a victim (for example a public or semi-trusted Wi-Fi network) positions themselves as a man-in-the-middle and presents a rogue TLS certificate, which the VitaFit app accepts because it trusts all certificates and any hostname. The attacker captures the victim's account session and health-related API data, then replays the captured session to delete the account's authentication record, locking the legitimate user out. A public PoC reference exists (GitHub security-research repo) but it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 04, 2026
Insecure TLS certificate validation in the VitaFit Android app (com.vt.vitafit) before 2.8.1.0 lets an unauthenticated attacker sitting on the same or an adjacent network path intercept and modify the app's HTTPS traffic, capturing account sessions and health-related API data; a stolen session can then be used to delete the account's authentication record and lock the legitimate user out. The root cause is baked into the app's default networking - a custom X509TrustManager that trusts every certificate combined with a hostname verifier that accepts any hostname - so no special configuration is needed for an attacker-supplied certificate to be accepted. A public PoC reference exists (a GitHub security-research repository); it is not verified as working exploit code, and no confirmed active exploitation was identified in the available data.
RemediationAI
Vendor-released patch: VitaFit for Android 2.8.1.0 - updating the app to 2.8.1.0 or later is the complete fix, since that release removes the trust-all X509TrustManager and the accept-any hostname verifier, and it is the remediation endpoint referenced by the VulnCheck advisory (https://www.vulncheck.com/advisories/vitafit-android-insecure-tls-certificate-validation) and the researcher repository (https://github.com/je-lv/vitafit-security-research). Distribution is via Google Play, so confirm the installed build reports 2.8.1.0 or higher after updating; no other patched version is listed in the available data. The sources describe no in-app configuration switch or server-side workaround for the vulnerable client, and the only complete fix stated is the app update - while devices remain on older builds, the exposure is bounded by the adjacent-network requirement, so users on untrusted Wi-Fi or behind a shared access point remain the highest-risk population until they upgrade. Organizations that manage the app should also treat session tokens and health-related API data from pre-2.8.1.0 clients as potentially compromised and invalidate affected accounts' sessions as part of the upgrade.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is CWE-295 (Improper Certificate Validation) in the Android client com.vt.vitafit, published by Shenzhen Shine Industrial Co., Ltd. (CPE cpe:2.3:a:shenzhen_shine_industrial_co.,_ltd.:vitafit). Android's standard HTTPS stack delegates trust decisions to an X509TrustManager and hostname matching to a HostnameVerifier; here the app ships a custom trust manager whose checkServerTrusted accepts any certificate chain and a verifier that returns true for any hostname, effectively downgrading HTTPS to unauthenticated encryption. Because the peer is never authenticated, an attacker who can occupy an on-path position (shared Wi-Fi, a controlled access point, ARP/DNS spoofing) can terminate TLS with a self-signed certificate, read and rewrite API requests and responses, and harvest bearer/session tokens - which the advisory says can be replayed to delete the account's authentication record and block subsequent logins. The assessed vector is CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H: attack complexity is low and no privileges or user interaction are required, but the adjacent-network precondition (AV:A) means the flaw is not reachable from the open internet, and impact is scoped to the app's own confidentiality, integrity and availability. The trigger path beyond these mechanics is not described in further detail in the available sources.
Know when Vitafit gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
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
Adjacent on-path position required (AV:A) with no auth or interaction (PR:N/UI:N, AC:L); accepting any cert enables full interception (C:H), traffic modification (I:H) and session-replay account deletion/lockout (A:H).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
2DescriptionCVE.org
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.
Articles & Coverage 1
Technical POC Analysis
CWE-295, improper certificate validation, in the VitaFit Android client (com.vt.vitafit).
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
The VitaFit Android app (versions before 2.8.1.0) contains a high-severity flaw that allows an attacker on the same network to intercept and modify sensitive health and account data, potentially locking users out of their accounts. This affects all users of the app, exposing personal health information and account integrity, and could lead to regulatory scrutiny and reputational damage. Leadership should prioritize remediation to protect user trust and comply with data protection obligations.
No vendor-released patch identified at time of analysis. Interim mitigations include advising users to avoid untrusted networks and use VPNs, implementing network monitoring for suspicious traffic, and restricting app usage to trusted networks where possible. However, these controls are limited because the vulnerability is in the app's default networking and may not be fully mitigable without a patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
VitaFit's cloud API before 2026-10-30 would issue a full authenticated session for any account whose linked Google or Fa
Broken access control in the VitaFit cloud API before the 2026-10-30 fix lets any authenticated account holder call POST
VitaFit's cloud API left its backing object storage bucket readable by anyone, so an attacker who locates the bucket can
Hardcoded third-party integration credentials in the VitaFit Android app before 2.8.1.0 expose embedded WeChat, Tencent
VitaFit Android before 2.8.1.0 exposes unencrypted m_session_id tokens in application backups, allowing anyone who obtai
Token interception in VitaFit Android before 2.8.1.0 allows a malicious app already installed on the device to register
The VitaFit cloud API, in builds prior to the 2026-10-30 release, returns other users' personally identifiable and healt
Authenticated users of the VitaFit fitness and smart-scale cloud API can read other accounts' data - email address, prof
An improper access control flaw in the VitaFit cloud API let authenticated holders of Cognito-issued AWS credentials wri
Stored cross-site scripting in the VitaFit cloud API (builds before 2026-10-30) lets an authenticated account holder upl
Cleartext HTTP handling in the VitaFit Android app (com.vt.vitafit) before 2.8.1.0 lets an attacker who holds a man-in-t
EUVD-2026-117146
GHSA-c27c-369r-q3m7
NVD
CVE.org
EPSS
Exploit-DB