On this page (6 sections)

CVE-2026-54378 describes a broken access control flaw in the VitaFit cloud API. According to the NVD record, any authenticated user could call a token endpoint and receive temporary AWS credentials that were not properly scoped, which opened the shared storage bucket to every account.

If you use the VitaFit app or service, or you build APIs that hand out cloud storage credentials to clients, this is worth a few minutes. The pattern behind it is common and easy to check for in your own systems.

What happened

The NVD description says the VitaFit cloud API, in its state before 2026-10-30, exposed a POST /front/user/s3/token/ endpoint. Any authenticated user who called it received temporary AWS credentials. Those credentials were improperly scoped, meaning they were not limited to the calling user's own files.

With them, the description states, an attacker could list the shared storage bucket and read or overwrite other users' stored files. That covers both unauthorized disclosure and unauthorized modification of data. The record was published on 2026-11-04.

Only one independent publisher covers this story so far, and the research here is limited to the NVD description. The record also references a GitHub research repository and a VulnCheck advisory. Details beyond the NVD text, such as what kinds of files were stored or whether anyone abused the flaw, are not confirmed here.

Why this class of bug is serious

Many mobile apps upload files straight to cloud storage. To avoid routing every upload through their own servers, the backend issues short-lived credentials to the app. This is a sound design only if each set of credentials is limited to what that one user may touch, for example a single prefix or object path.

Here the credentials were broader than the user. Authentication alone was enough, so anyone able to create or hold an ordinary account could step into the storage of every other account. Because the access was write-capable per the description, an attacker could also tamper with or replace files, which is harder to notice than a read.

Who is affected

  • People with VitaFit accounts whose files are kept in the shared storage bucket. The research does not say which file types are stored.
  • VitaFit as the operator, which controls the fix. The record indicates the issue applies to the API before 2026-10-30, so the fix is on the service side rather than something users install.
  • Developers and site owners with similar designs: any API that mints temporary AWS (or other cloud) credentials for logged-in users.

We have no information about whether a client app update is needed. The research does not provide patch instructions for end users, so check the vendor's own communications.

What to do now

If you are a VitaFit user

  1. Watch for an official statement from VitaFit about this issue and whether data was accessed.
  2. Consider what you uploaded to the service and whether any of it is sensitive.
  3. Change your password and enable any extra sign-in protection the app offers, as a general precaution.
  4. Review your account for files or changes you did not make, since the flaw allowed overwriting.
  5. Keep the app updated from the official store listing.

If you run an API that issues cloud credentials

Use this review to check whether the same mistake could exist in your code. The point is to confirm that each credential set is bound to one user and one storage path.

  1. Find every endpoint that returns temporary credentials or pre-signed URLs.
  2. Confirm the issued policy restricts access to the caller's own prefix, not the whole bucket.
  3. Deny bucket listing for client credentials unless it is strictly required and scoped.
  4. Prefer pre-signed URLs for single objects with short expiry over broad credentials.
  5. Enable object versioning and access logging on the bucket so overwrites can be detected and reverted.
  6. Test with two ordinary accounts and confirm neither can see the other's objects.
Caution. Do not test access to other people's data on a live service you do not own. Run these checks only on systems you operate, using accounts you created for the purpose.

Detection and monitoring

If you operate a bucket like this, review storage access logs for credential sessions that list the bucket or touch objects outside the owning user's path. Unexpected list operations and writes to objects an account never created are the signs to look for. Versioning lets you compare earlier object versions against current ones.

On the web side, outside tools cannot see inside a mobile API's storage permissions, so treat scans and monitoring as a complement to access reviews rather than a replacement. If your own site exposes an API, a read-only security scan and header and certificate monitoring help you catch drift in what you expose, and the guide to website security for small business covers the wider basics.

What we still do not know

  • Whether the flaw was exploited in the wild. The research does not say either way.
  • The exact fix applied by VitaFit and when it reached all users, beyond the 2026-10-30 boundary in the record.
  • How many accounts or files were reachable, and what they contained.
  • Whether users need to take any action in the app.

We will treat claims beyond the NVD text as unconfirmed until the vendor or the linked advisory states them clearly.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-54378: VitaFit cloud API before 2026-10-30 contained a broken access control vulnerability that allows any authenticated user to obtain temporary AWS credentials by…nvd.nist.gov ·
  • CVE-2026-54378
  • VitaFit
  • broken access control
  • AWS S3
  • API security