Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/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
Network-accessible cloud endpoint requires no authentication or user interaction; impact limited to low confidentiality via account access, with no integrity or availability impact supported by the description.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
Lifecycle Timeline
2DescriptionCVE.org
The Mira cloud authentication endpoints do not enforce per-account rate limiting, per-IP throttling, or account lockout after repeated failed login attempts. An attacker can use brute-force methods to obtain gain access to user accounts.
AnalysisAI
Brute-force credential attacks against Mira's cloud authentication endpoints are unrestricted due to the complete absence of per-account rate limiting, per-IP throttling, and account lockout controls, as disclosed in CISA ICS Medical Advisory ICSMA-26-223-01. Affected products include Mira Firmware 1.7.1.47 and Mira Android App 4.5.15.4 from Quanovate Tech Inc. (operating as Mira / Mira Care), a healthcare-focused IoT platform. An unauthenticated remote attacker can systematically enumerate credentials at arbitrary scale to gain unauthorized access to user accounts, with no public exploit code or CISA KEV listing identified at time of analysis.
Technical ContextAI
CWE-307 (Improper Restriction of Excessive Authentication Attempts) describes the failure to impose meaningful limits on repeated login attempts, a foundational authentication control absent from the Mira cloud backend. The two affected products - Mira Firmware (CPE: cpe:2.3:a:quanovate_tech_inc._(operating_as_mira_/_mira_care):mira_firmware:*:*:*:*:*:*:*:*) and Mira Android App (CPE: cpe:2.3:a:quanovate_tech_inc._(operating_as_mira_/_mira_care):mira_android_app:*:*:*:*:*:*:*:*) - share cloud authentication endpoints, meaning both client surfaces expose the same vulnerable backend. Standard mitigations such as exponential backoff, CAPTCHA challenges, temporary account suspension, or IP-level cooldown are all absent according to the advisory. In a healthcare IoT context, these cloud accounts are likely linked to patient data, device configuration, or care coordination workflows, raising the consequence profile beyond what the raw CVSS impact metrics alone convey. The ICS-CERT classification of this advisory underscores the operational technology and medical device angle.
RemediationAI
Consult CISA ICS Medical Advisory ICSMA-26-223-01 at https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-223-01 for vendor-specific patch guidance; patch available per vendor advisory, but no exact patched firmware or app version number was present in the available source data and fix version is not independently confirmed. As compensating controls pending patch deployment, operators should enforce strong, unique passwords for all Mira accounts to materially increase brute-force search space, and enable multi-factor authentication if the Mira platform supports it, as even weak rate limiting at the MFA layer would substantially raise attack cost. Organizations should configure alerting on anomalous authentication volume against the Mira cloud endpoints and consider restricting endpoint access to known IP ranges via network egress controls or firewall policy - note that IP restriction may conflict with mobile app usability for roaming users. A web application firewall with credential stuffing detection rules can throttle automated attempt volume at the perimeter, though this is a bypass-able control rather than a fix. The CSAF advisory at https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsma-26-223-01.json may contain additional vendor-recommended mitigations.
More in Mira Firmware
View allAuthentication bypass in the Mira fertility-tracking cloud API allows any remote attacker to take over user accounts by
Session token exposure in the Mira Android app (Quanovate Tech Inc.) leaks live authentication credentials to third-part
Firmware version spoofing in the Mira cloud API allows authenticated users to submit arbitrary firmware version strings
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-56981
GHSA-r6p2-jjcr-jm7c