Skip to main content

VitaFit Cloud API EUVDEUVD-2026-117163

| CVE-2026-54382 MEDIUM
Incorrect Privilege Assignment (CWE-266)
2026-11-04 VulnCheck GHSA-vfgc-8vj5-8w5w
6.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

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

  1. Access
    Authenticate to VitaFit and obtain Cognito AWS credentials
  2. Exploit
    Assume over-broad IAM role (optionally pivot via CVE-2026-54378)
  3. Execution
    Issue s3:PutObject outside own folder
  4. Impact
    Overwrite other users' objects, destroying original content

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
Exploitation Conditions

Requires an authenticated VitaFit identity: the attacker must hold Cognito-issued AWS credentials (PR:L), reachable over the network API (AV:N) with no user interaction. The core prerequisite is the misconfigured Cognito-issued IAM role whose policy grants s3:PutObject across the entire shared bucket rather than being restricted to the caller's own folder. Affected scope is the VitaFit cloud API before the 2026-10-30 fix. The practical, impactful attack - overwriting a SPECIFIC other user's objects - is limited by needing that victim's credentials, which the description states are obtained via CVE-2026-54378; without chaining, an attacker can still write across the shared bucket but targeting is constrained. Limiting factors: valid authentication is mandatory (not unauthenticated), impact is restricted to integrity/overwrite (no read access to others' data, no stated availability loss of the service itself), and exposure ends with the patched API.

Impact

This is a medium-severity integrity flaw (input CVSS 4.0 base 6.3), and the signals consistently point to a moderate, not urgent, priority. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) shows a network-reachable, low-complexity issue that nevertheless requires authentication (PR:L) - an attacker needs a valid VitaFit/Cognito identity, so this is not unauthenticated mass-exploitable. Impact is narrow: confidentiality and availability of the vulnerable system are N, and the only material impact is subsequent-system integrity (SI:H) - the ability to overwrite other users' objects in the shared S3 bucket. The vuln.today Decision label is 'monitor', which aligns with the limited impact and authentication requirement. No CISA KEV listing is present and no EPSS score was supplied, so widespread or automated exploitation is not indicated. A public PoC reference exists but is not verified as working exploit code. A key compounding factor is explicit in the description: practical cross-user abuse depends on obtaining another user's credentials via CVE-2026-54378, so real-world risk is gated on that chained flaw. Net: a genuine but contained integrity/data-destruction issue in a niche consumer product, not a high-urgency network-worm candidate. Note one data conflict - the 'Information Disclosure' tag contradicts the CVSS vector, which records no confidentiality impact (VC:N); this is a data-integrity/overwrite bug, not a disclosure bug.

Exploit ScenarioDerived

An attacker who holds valid VitaFit Cognito credentials (and, per the description, credentials for a target account obtained via CVE-2026-54378) assumes the over-privileged AWS role and issues s3:PutObject calls against paths outside their own folder in the shared bucket. Because the role is not scoped per-user, they overwrite another user's stored objects, destroying the original content without tripping deletion protections. A public PoC reference exists; it is not verified as working exploit code.

Monitor Track and reassess. Why: Vendor states no customer action required.
Patch available 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Nov 04, 2026

An improper access control flaw in the VitaFit cloud API let authenticated holders of Cognito-issued AWS credentials write objects anywhere in the shared S3 bucket instead of being confined to their own folder, allowing one user's stored content to be overwritten with another's. The affected scope is the VitaFit cloud API before the fix dated 2026-10-30; the weakness is a bucket-wide s3:PutObject grant in the Cognito-mapped IAM role (CWE-266). The input scores the issue 6.3 (CVSS 4.0), exploitation requires a valid authenticated VitaFit identity (PR:L), and the most damaging variant - overwriting a specific victim's objects - depends on credentials said to be obtained through CVE-2026-54378. A public proof-of-concept reference exists (github.com/je-lv/vitafit-security-research) but is not verified as working exploit code, there is no KEV listing, and the priority signal is monitor.

RemediationAI

Remediation is on the vendor side: exposure ends with the VitaFit cloud API as patched on 2026-10-30, so operators or users of affected accounts should confirm that their backend/build is at or after that fix rather than a pre-2026-10-30 release; there is no client-side patch identified in the available data, and affected users should update the VitaFit Android app and re-authenticate so that Cognito issues credentials from the corrected role. The 2026-10-30 fix is vendor-released; the specific policy change is not enumerated in the supplied sources. The controlling weakness is the IAM policy behind the Cognito identity mapping, which must scope s3:PutObject to the caller's own prefix (commonly templated on the Cognito identity ID or sub claim) instead of the bucket ARN. Where the vendor's fix is not yet in place, the actionable compensating control is on the bucket policy/role rather than on the app: replacing the bucket-wide write grant with a prefix-conditioned grant or explicit Deny on cross-prefix PutObject, with the trade-off that identities whose legitimate paths do not match the prefix template will lose write access until the mapping is corrected. Because the targeted-overwrite scenario chains through credentials obtained via CVE-2026-54378, credential rotation for Cognito-issued AWS sessions also limits reuse. Note that enabling object versioning alone is a weak control here, since the available data indicates the overwrite path did not trigger deletion protections; verify behavior before relying on it. Reference advisory: https://www.vulncheck.com/advisories/vitafit-cloud-api-aws-iam-misconfiguration-via-cognito-s3-access.

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

VitaFit's mobile backend (Android package com.vt.vitafit) issues AWS credentials to authenticated users through Amazon Cognito identity pools, which map an identity to an IAM role. In a correctly configured pool the role's S3 permissions are scoped to a per-identity prefix (typically templated with the Cognito identity ID or sub claim); here the role granted s3:PutObject on the whole shared bucket ARN, a textbook incorrect privilege assignment (CWE-266) that converts a per-tenant folder boundary into a bucket-wide write capability. The CVSS 4.0 vector CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N describes network reachability, low attack complexity, no user interaction, and low privileges, with the only scored impact being high subsequent-system integrity - notably no confidentiality impact and no availability impact, so this is an overwrite/tampering problem rather than a data-exfiltration or denial-of-service problem. The trigger mechanics beyond the misconfigured role - for example whether overwriting requires knowing a victim's object key - are not described in the available sources. Because the description notes the overwrite did not trip deletion protections, existing guardrails evidently did not treat in-place PutObject as a destructive action.

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 6.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N
vuln.today AI 7.7 HIGH

Authenticated Cognito user (PR:L) over the network API (AV:N/AC:L); the role lets one user modify other users' data, a scope change (S:C), with integrity-only impact (I:H, C:N/A:N).

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

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

Lifecycle Timeline

2
Patch available
Nov 04, 2026 - 23:02 EUVD
CVE Published
Nov 04, 2026 - 22:18 cve.org
MEDIUM 6.3

DescriptionCVE.org

VitaFit cloud API before 2026-10-30 contained an improper access control vulnerability in its Cognito-issued AWS role that allows authenticated attackers to perform s3:PutObject operations across the entire shared bucket instead of being restricted to their own folder. Attackers can overwrite other users' objects in the shared S3 bucket using credentials obtained via CVE-2026-54378, destroying original content without triggering deletion protections.

Threat Intelligence Overview

EPSS Score
0.2%
Top 88% exploitable
Prevalence
Low
niche consumer smart-scale app tied to a single IoT vendor's cloud
Service Type
Hosted
Vendor-managed, no client patch needed
Exploit
POC
Public exploit code exists
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 MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
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
No
Human Impact· derived
Medium

Priority Score

52
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0
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-54381 HIGH POC
8.7 Nov 04

VitaFit's cloud API left its backing object storage bucket readable by anyone, so an attacker who locates the bucket can

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