VitaFit Cloud API Broken Access Control via S3 Token Endpoint
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2026-10-30
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. VitaFit cloud API version before 2026-10-30 Attacker must be an authenticated user
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
CVE-2026-54378 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.3 (critical) and affects VitaFit; fixed in 2026-10-30.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2026-10-30
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
VitaFit's cloud API contains a broken access control flaw in its S3 token endpoint that lets any logged-in user obtain temporary AWS credentials that are scoped too broadly. Attackers reach it remotely with a low-privilege account and can then read or overwrite other users' stored files in the shared storage bucket.
Read the original description
VitaFit cloud API before 2026-10-30 contained a broken access control vulnerability that allows any authenticated user to obtain temporary AWS credentials by calling the POST /front/user/s3/token/ endpoint. Attackers can use these improperly scoped credentials to list the shared storage bucket and read or overwrite other users' stored files, enabling unauthorized cross-user data access and manipulation.
What to do
Check whether your setup matches what the bug needs.
VitaFit cloud API version before 2026-10-30 Attacker must be an authenticated userUpgrade to a fixed version: 2026-10-30.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Shenzhen Shine Industrial Co., Ltd. VitaFit
fixed in 2026-10-30
Evidence 3
- Exploit
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-54378
Is CVE-2026-54378 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: cve.now feed data
What does this mean?
Any signed-in user of the VitaFit cloud API can call the POST /front/user/s3/token/ endpoint and receive temporary AWS credentials that are scoped too broadly. With those credentials, the user can list the shared storage bucket and read or overwrite other users' stored files.Source: vulncheck.com
Which versions are affected by CVE-2026-54378?
VitaFit: before 2026-10-30.Source: cve.now feed data
Am I affected, and how do I check?
The facts list VitaFit cloud API builds before 2026-10-30 as affected, and the attacker must be an authenticated user. To check a version, compare the cloud API build date against 2026-10-30; the facts do not name a specific command or setting for this.Source: vulncheck.com
How do I fix CVE-2026-54378?
Update the VitaFit cloud API to a build dated 2026-10-30 or later, which is the fixed version listed in the facts. No workaround is listed in the facts.Source: vulncheck.com