Skip to main content

VitaFit EUVDEUVD-2026-117160

| CVE-2026-54381 HIGH
Incorrect Permission Assignment for Critical Resource (CWE-732)
2026-11-04 VulnCheck GHSA-qg7r-2qmf-p77f
8.7
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Discover public storage bucket endpoint
  2. Delivery
    Send unauthenticated list request
  3. Exploit
    Enumerate 129,947 objects
  4. Execution
    Download user profile images
  5. Impact
    Exfiltrate sensitive personal data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Permission assignment review
Exploitation Conditions

No special conditions beyond network reachability of the bucket - exploitation is remote and unauthenticated (PR:N/UI:N) against the publicly misconfigured cloud storage bucket backing the VitaFit cloud API, requiring only that the attacker discover or guess the bucket's endpoint/name. The limiting factors are: the attacker must locate the specific bucket (not advertised in the CVE), and the exposure is time-bounded - the description scopes it to the state 'before 2026-10-30', so an environment updated past the vendor's remediation should no longer expose the objects. Impact is confined to confidentiality of stored files (user profile images and associated personal data); no write/integrity or availability consequence is described.

Impact

The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N) with VC:H and no integrity or availability impact accurately reflects a pure confidentiality exposure: anyone on the network can list and download files from a misconfigured, publicly readable cloud storage bucket with no credentials, no user interaction, and low complexity - consistent with the CWE-732 (incorrect permission assignment) root cause and the description. Signals, however, do not all point the same way: there is no CISA KEV listing and no EPSS score supplied, and the vuln.today decision label is 'monitor' rather than act_now/emergency, indicating no evidence of active or automatable mass exploitation at the time of analysis. A PoC reference exists (a GitHub security-research repo) but it is not verified as working exploit code. The practical takeaway: this is a genuine, high-impact data-exposure issue (over 126,881 user profile images and ~129,947 total objects already reported as exposed) rather than an inflated high-CVSS score, but the real-world urgency is tempered by the 'monitor' priority, the absence of KEV/EPSS corroboration, and the fact that the reported exposure window ('before 2026-10-30') may already be closed by the vendor fix. EPSS is missing, so widespread automated scanning probability cannot be quantified from the input.

Exploit ScenarioDerived

A remote, unauthenticated attacker discovers the VitaFit cloud storage bucket name/URL and issues list and object-download requests directly against it, retrieving user-uploaded profile images and other stored files without any credentials. A public PoC reference exists (VulnCheck/GitHub security research), though it is not verified as working exploit code, so the barrier to reproducing the enumeration is low. Low attack complexity and no required interaction make bulk harvesting of the ~129,947 objects straightforward once the bucket is located.

Monitor Track and reassess. Why: Vendor states no customer action required.
1 PoC candidate (unverified) Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 04, 2026

VitaFit's cloud API left its backing object storage bucket readable by anyone, so an attacker who locates the bucket can enumerate and download stored files - 129,947 objects, of which 126,881 are user-uploaded profile images - with no credentials and no user interaction, exposing personal data tied to app users. The root cause is an incorrect permission assignment (CWE-732) on the storage bucket rather than a code-level memory or injection flaw, and the impact is confined to confidentiality: no write, integrity or availability effect is described, matching the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N against a vendor score of 8.7. Exploitation status: a public PoC reference exists; it is not verified as working exploit code, there is no CISA KEV listing, and the issue is tracked at monitor priority. Anyone running the affected VitaFit cloud API in its pre-2026-10-30 state, and any user whose image was stored in the bucket, should be considered within scope.

RemediationAI

No vendor-released patch version is identified in the available data; the supplied description instead scopes the vulnerable state to VitaFit cloud API builds before 2026-10-30, so the primary action is to confirm the deployment is at or past that remediated state and to verify the fix directly by requesting the bucket anonymously and confirming that both listing and object retrieval are denied - consult https://www.vulncheck.com/advisories/vitafit-cloud-api-storage-bucket-unauthenticated-access-information-disclosure for the vendor's stated remediation. Where an upgrade cannot be applied immediately, remove every public or AllUsers grant of list and get permission from the bucket ACL and bucket policy and add an explicit deny for anonymous principals at the bucket or IAM layer; the trade-off is that any direct-to-bucket delivery of profile images, including CDN or client caching paths, will start returning errors, so images must be re-served through the authenticated API using short-lived signed URLs, at the cost of added latency and loss of edge caching. Enable storage access logging before lockdown so the enumeration and download window can be reconstructed, and because objects already retrieved cannot be recalled, treat the exposed profile images and associated personal data as compromised and notify affected users. Rotating any credentials or pre-signed URLs embedded in the mobile client should accompany the permission change, since those values remain extractable from installed app versions regardless of the bucket fix.

Affected VersionsENISA

VitaFit 0 <2026-10-30

Affected Packages

euvd vitafit fix: 2026-10-30

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 flaw sits in the storage tier behind the VitaFit cloud API rather than in the API logic itself. Cloud object storage permissions are expressed through bucket ACLs and bucket/object policies; CWE-732 (Incorrect Permission Assignment for Critical Resource) describes exactly this class - a bucket policy or ACL that grants list and get rights to an anonymous or public principal, so an unauthenticated request directly against the storage endpoint returns an object listing and then the objects themselves, bypassing the API's own authentication entirely. The CPE data attributes the product to Shenzhen Shine Industrial Co., Ltd. as vendor for 'vitafit', and the referenced Google Play listing (com.vt.vitafit) indicates the bucket backs a consumer mobile application, which is why the object population is dominated by 126,881 user-uploaded profile images out of 129,947 total objects. The trigger is described in the available sources: anonymous listing and download of bucket contents requires only that the attacker identify the bucket name or endpoint; nothing about write access, code execution or object tampering is reported. Exposure is time-bounded by the vendor's remediation date - the description scopes the vulnerable state to releases before 2026-10-30, so an environment already moved past that remediation should no longer serve the objects anonymously, though the exact provider and bucket configuration are not specified in the supplied 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

Vendor (VulnCheck) PRIMARY 8.7 HIGH
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
vuln.today AI 7.5 HIGH

Remote unauthenticated read of a public bucket with no interaction (AV:N/AC:L/PR:N/UI:N); confidentiality-only exposure (C:H, I:N, A:N) with no scope change.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Nov 04, 2026 - 23:02 EUVD
CVE Published
Nov 04, 2026 - 22:15 cve.org
HIGH 8.7

DescriptionCVE.org

VitaFit cloud API before 2026-10-30 contained a misconfigured cloud storage bucket vulnerability that allows unauthenticated attackers to list and download stored files without authentication. Attackers can enumerate the publicly accessible bucket containing 129,947 objects, including 126,881 user-uploaded profile images, to access sensitive personal data without credentials.

Technical POC Analysis

No patch diff, no commit, and no runnable PoC are present in the supplied evidence.

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

Why It Matters

VitaFit's cloud API stores user-uploaded profile images in a publicly readable object storage bucket, exposing personal data for over 126,000 users. This is a high-severity confidentiality breach affecting all app users who have uploaded images. Leadership should care due to privacy violation, regulatory exposure (GDPR/CCPA), and potential reputational harm.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include restricting bucket access to authenticated users (e.g., via signed URLs or IAM policies), enabling logging and monitoring of bucket access, and notifying affected users to be vigilant for phishing or identity theft.

Threat Intelligence Overview

EPSS Score
0.4%
Top 63% exploitable
Prevalence
Low
niche consumer smart-scale app, modest user base (~130k objects)
Service Type
Hosted
Vendor-managed, no client patch needed
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

64
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-54384 CRITICAL POC
9.3 Nov 04

VitaFit's cloud API before 2026-10-30 would issue a full authenticated session for any account whose linked Google or Fa

CVE-2026-54378 CRITICAL POC
9.3 Nov 04

Broken access control in the VitaFit cloud API before the 2026-10-30 fix lets any authenticated account holder call POST

CVE-2026-54374 HIGH POC
8.7 Nov 04

Hardcoded third-party integration credentials in the VitaFit Android app before 2.8.1.0 expose embedded WeChat, Tencent

CVE-2026-54372 HIGH POC
8.7 Nov 04

Insecure TLS certificate validation in the VitaFit Android app (com.vt.vitafit) before 2.8.1.0 lets an unauthenticated a

CVE-2026-54375 HIGH POC
8.6 Nov 04

VitaFit Android before 2.8.1.0 exposes unencrypted m_session_id tokens in application backups, allowing anyone who obtai

CVE-2026-54376 HIGH POC
8.2 Nov 04

Token interception in VitaFit Android before 2.8.1.0 allows a malicious app already installed on the device to register

CVE-2026-54383 HIGH POC
7.1 Nov 04

The VitaFit cloud API, in builds prior to the 2026-10-30 release, returns other users' personally identifiable and healt

CVE-2026-54377 MEDIUM POC
6.9 Nov 04

Authenticated users of the VitaFit fitness and smart-scale cloud API can read other accounts' data - email address, prof

CVE-2026-54382 MEDIUM POC
6.3 Nov 04

An improper access control flaw in the VitaFit cloud API let authenticated holders of Cognito-issued AWS credentials wri

CVE-2026-54380 MEDIUM POC
5.1 Nov 04

Stored cross-site scripting in the VitaFit cloud API (builds before 2026-10-30) lets an authenticated account holder upl

CVE-2026-54373 MEDIUM POC
5.1 Nov 04

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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy