EUVD-2026-57006

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...

EUVD-2026-57005

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...

EUVD-2026-56982

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...

EUVD-2026-57009

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...

EUVD-2026-56981

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...

EUVD-2026-57007

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...

EUVD-2026-56980

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...

CVE-2026-66875

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...

CVE-2026-66875

The CVE-2026-66875 entry concerns the Mira hormone monitor firmware v1.7.1.47 (build 01070147). A remote unauthenticated attacker within BLE range (≈10–30 m) can: rebind the device to an attacker-controlled account; extract stored hormone measurements in cleartext; cause a denial-of-service via m...

CVE-2026-66098

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-66098

The CVE affects the Mira hormone monitor device firmware. A 0x01 BLE write from any unauthenticated central triggers reboot into bootloader mode, enabling a denial-of-service condition and potentially disrupting ovulation tracking and fertility monitoring workflow. The sources describe the vulner...

CVE-2026-67558

The CVE concerns the Mira Android companion app version 4.5.15.4, which authenticates to the paired Mira hormone analyzer via a simple substring match on the BLE advertising name. There is no cryptographic periphery authentication, MAC allowlist, or bonded-identity check described in the provided...

CVE-2026-67558

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...

CVE-2026-67568

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-67568

The CVE-2026-67568 entry concerns Mira Android APK v4.5.15.4, where an attacker could read/write reproductive health profiles from internet-connected hosts, enabling forgery, deletion, or destruction of health information. Public metrics show a critical impact (CVSS 3.1/3.1: 9.1; CVSS 4.0/4.0: 9....

CVE-2026-68067

The CVE concerns Mira Hormone Monitor / Mira Android App with a weak authentication issue in the cloud login API. The login endpoint accepts any format-valid string in the password field and returns a live active session token for the account matching the supplied email address. Attack scenario: ...

CVE-2026-68067

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...

CVE-2026-66340

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-66340

CVE-2026-66340 affects the Mira ecosystem where the cloud authentication endpoints do not enforce per-account rate limiting, per-IP throttling, or account lockout after repeated failed login attempts. This enables brute-force login attempts that can lead to unauthorized access to user accounts. T...

CVE-2026-64934

CVE-2026-64934 affects the Mira Hormone Monitor ecosystem, specifically the Mira Android App and related cloud API. The root cause is reliance on the firmware version reported by the companion app without independent attestation from the device itself. An authenticated attacker could submit arbit...