CVERadar
CRITICAL · CVSS 4.0 9.3EPSS 0.23% (p14)Threat level 47

CVE-2026-54378: CVE-2026-54378: VitaFit cloud API before 2026-10-30 contained a broken access control vulnerability that a…

Unknown · VitaFit · NVD published 2026-11-05 · posted 2026-11-05 · last modified 2026-11-05

CVE-2026-54378 at a glance

CVE-2026-54378 is a critical-severity vulnerability in VitaFit, with a CVSS 4.0 base score of 9.3. NVD published it on 2026-11-05 and classifies the weakness as CWE-522. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.23% (percentile 13.9, scored 2026-11-05). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 47/100.

What it is

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.

WeaknessCWE-522 definition
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X (source: VulnCheck)
ATT&CK tacticsn/a

No ATT&CK techniques could be mapped or inferred for this CVE yet.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources