Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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 API requires authenticated session (PR:L); integrity impact added for falsification of vendor fleet version records, absent from the source CVSS 4.0 assessment.
Primary rating from Vendor (icscert).
CVSS VectorVendor: icscert
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/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
Lifecycle Timeline
2DescriptionCVE.org
The Mira cloud API accepts the firmware version reported by the companion app as authoritative for a given device, without independently attesting the version from the device itself. An authenticated attacker could submit arbitrary firmware version strings for their own device, allowing them to evade vendor-side vulnerable-fleet analytics, suppress security update prompts to the user, and misrepresent patch-adoption metrics.
AnalysisAI
Firmware version spoofing in the Mira cloud API allows authenticated users to submit arbitrary firmware version strings for their own registered devices, bypassing server-side validation entirely. Affected products are Mira Firmware 1.7.1.47 and Mira Android App 4.5.15.4 by Quanovate Tech Inc., operating in a medical IoT context and reported under CISA ICS-CERT advisory ICSMA-26-223-01. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires a valid, authenticated Mira user account (CVSS PR:L confirmed). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 4.0 score of 5.3 (Medium) reflects that exploitation requires an authenticated session (PR:L), which constrains the attack surface to registered Mira account holders with at least one enrolled device. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An authenticated Mira account holder uses a proxy tool (such as Burp Suite) to intercept the companion Android app's API call that reports device firmware version to the Mira cloud backend, then replaces the version string with an arbitrarily higher or targeted value before forwarding the request. The cloud backend records the spoofed version as authoritative, causing update prompts to be suppressed and the device to appear fully patched in vendor fleet analytics. … |
| Remediation | No specific patched version number is independently confirmed from the available intelligence; the CISA ICS-CERT advisory ICSMA-26-223-01 (https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-223-01) is the authoritative source for vendor-issued remediation guidance and should be consulted directly for upgrade paths. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in Mira Firmware
View allAuthentication bypass in the Mira fertility-tracking cloud API allows any remote attacker to take over user accounts by
Brute-force credential attacks against Mira's cloud authentication endpoints are unrestricted due to the complete absenc
Session token exposure in the Mira Android app (Quanovate Tech Inc.) leaks live authentication credentials to third-part
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-56980
GHSA-v72c-jrwc-x8qx