CVE-2026-66875 is a high-severity Bluetooth Low Energy vulnerability affecting the Mira hormone monitor ecosystem, specifically Mira firmware version 1.7.1.47 build 01070147 and the associated Android app version 4.5.15.4. A remote attacker within BLE proximity can interact with the device without authentication and silently rebind it to an attacker-controlled account. The same weakness also permits extraction of stored hormone measurements in cleartext, denial of service through malformed or undocumented command opcodes, and passive user tracking because the device uses a static random BLE address that does not rotate. The vulnerability is consistent with missing authentication on security-sensitive BLE operations and inadequate protection of locally stored sensitive data and device privacy mechanisms.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity vulnerability in the Mira Hormone Monitor ecosystem that could allow extraction of stored hormone measurements, denial of service, and passive user tracking.
A vulnerability in Mira hormone monitor firmware that allows a nearby unauthenticated attacker over BLE to rebind the device to an attacker-controlled account, read stored hormone measurements in cleartext, trigger denial of service, and track the user due to a non-rotating static BLE address.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.