Vulnerabilidades de Quanovate Tech Inc. (operating as Mira / Mira Care)
CVEs publicadas que afetam produtos de Quanovate Tech Inc. (operating as Mira / Mira Care): 8 registro(s), com severidade, exploração e correções.
CVE-2026-68067
Crítica · 9.8
CWE-1390 11/08/2026
Mira Hormone Monitor, Mira Android App Weak Authentication
The login endpoint on the Mira cloud API accepts any format-valid string in the password field and returns a live active session token for the account matching the supplied email address. An attacker could use an email address to control cloud accounts and access hormone record information and account settings.
CVE-2026-67568
Crítica · 9.1
CWE-798 11/08/2026
Mira Hormone Monitor, Mira Android App Use of Hard-coded Credentials
The distributed Mira Android APK v4.5.15.4 allows an attacker read/write access to reproductive health profiles from internet connected hosts, which could result in forgery, deletion, or destruction of health information.
CVE-2026-67558
Alta · 7.4
CWE-290 11/08/2026
Mira Hormone Monitor, Mira Android App Authentication bypass by spoofing
The Mira Android companion app v4.5.15.4 identifies the paired Mira hormone analyzer by performing a substring match against the BLE advertisement name only, with no cryptographic peripheral authentication, MAC allowlist, or bonded-identity check. An attacker could capture live session token information and inject forged hormone measurements into the victim's cloud record and clinical trend view.
CVE-2026-66875
Alta · 8.8
CWE-306 11/08/2026
Mira Hormone Monitor, Mira Android App Missing authentication for critical function
In the Mira hormone monitor device firmware v1.7.1.47 build 01070147, a remote unauthenticated attacker within BLE range (approximately 10–30 meters) can silently rebind the device to an attacker-controlled account, extract stored hormone measurements in cleartext, cause a denial-of-service via malformed or undocumented command opcodes, and passively track the user via a static random BLE address that never rotates.
CVE-2026-66340
Média · 5.3
CWE-307 11/08/2026
Mira Hormone Monitor, Mira Android App Improper restriction of excessive authentication attempts
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.
CVE-2026-66098
Média · 6.5
CWE-306 11/08/2026
Mira Hormone Monitor, Mira Android App Missing authentication for critical function
The Mira hormone monitor device firmware accepts a 0x01 write from any BLE central without authentication, causing the device to reboot into bootloader mode. An attacker could cause a denial-of-service condition or disrupt ovulation tracking and fertility monitoring workflow.
CVE-2026-64934
Média · 4.3
CWE-807 11/08/2026
Mira Hormone Monitor, Mira Android App Reliance on untrusted inputs in a security decision
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.
CVE-2026-66832
Média · 6.5
CWE-598 11/08/2026
Mira Hormone Monitor, Mira Android App Use of GET request method with sensitive query strings
When the Mira Android app opens in-app WebView content (e.g., shop redirect flows), the user's live session token is appended to the URL as a query string parameter, and a persistent user identifier is included in the WebView's User-Agent header. Both are then transmitted to third-party web properties, referrer logs, and any JavaScript running in the WebView context.