Skip to main content
VulnerabilityPublished

CVE-2026-54376: Shenzhen Shine Industrial VitaFit · Improper Export of Android Application Components

Affects Shenzhen Shine Industrial VitaFitSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2.8.1.0 soon.

Data as of 5 Nov 2026, 00:16 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.2
CNA (VulnCheck)CVSS 3.18.2
Patch
Available – fixed in 2.8.1.0
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Shenzhen Shine Industrial VitaFit to 2.8.1.0.

Affected software

ProductAffectedFixed in
Shenzhen Shine Industrial Co., Ltd.VitaFitAffected
  • <2.8.1.0
Fixed in
  • 2.8.1.0

AI-suggested

Upgrade the VitaFit Android application to version 2.8.1.0 or later, where this vulnerability is fixed. No other mitigation actions are indicated.

Description

VitaFit Android application versions before 2.8.1.0 have an insecure custom URI scheme vulnerability. This flaw allows a malicious app to intercept Fitbit login tokens by registering the same callback scheme (vitafit://vtio.cn). Attackers can capture a 30-day Fitbit authorization token with weight scope, enabling them to read, create, and delete the victim's weight and body-fat records via the Fitbit Body API. The vulnerability is fixed in version 2.8.1.0.

References

Community reviews

Loading reviews…