CVE-2026-66875

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-12. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Mira Hormone Monitor, Mira Android App | CISA

Mira Hormone Monitor, Mira Android App | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-223-01

Vendor Advisories for CVE-2026-66875(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 27× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 22:52 UTCGHSA enrichment
  3. 2026-08-20 11:45 UTCGHSA enrichment
  4. 2026-08-20 00:36 UTCEG score recompute
  5. 2026-08-20 00:36 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:28 UTCGHSA enrichment
  8. 2026-08-19 02:21 UTCGHSA enrichment
  9. 2026-08-18 15:14 UTCEG score recompute
  10. 2026-08-18 15:13 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 03:03 UTCGHSA enrichment
  13. 2026-08-17 15:56 UTCEG score recompute
  14. 2026-08-17 15:56 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 04:49 UTCGHSA enrichment
  17. 2026-08-16 17:42 UTCEG score recompute
  18. 2026-08-16 17:42 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 06:34 UTCEG score recompute
  21. 2026-08-16 06:34 UTCGHSA enrichment
  22. 2026-08-15 19:28 UTCGHSA enrichment
  23. 2026-08-15 08:21 UTCEG score recompute
  24. 2026-08-15 08:21 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 18 more
  1. 2026-08-14 21:13 UTCGHSA enrichment
  2. 2026-08-14 10:06 UTCGHSA enrichment
  3. 2026-08-13 22:59 UTCEG score recompute
  4. 2026-08-13 22:59 UTCGHSA enrichment
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 11:52 UTCGHSA enrichment
  7. 2026-08-13 00:45 UTCEG score recompute
  8. 2026-08-13 00:45 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 13:38 UTCEG score recompute
  11. 2026-08-12 13:38 UTCGHSA enrichment
  12. 2026-08-12 12:55 UTCEG score recompute
  13. 2026-08-12 12:55 UTCGHSA enrichment
  14. 2026-08-12 09:27 UTCEG score recompute
  15. 2026-08-12 09:27 UTCGHSA enrichment
  16. 2026-08-11 22:20 UTCEG score recompute
  17. 2026-08-11 21:45 UTCEG score recompute
  18. 2026-08-11 21:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-66875?
CVE-2026-66875 is a high vulnerability published on August 11, 2026. 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…
When was CVE-2026-66875 disclosed?
CVE-2026-66875 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66875 actively exploited?
CVE-2026-66875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.4% of all scored CVEs.
What is the CVSS score of CVE-2026-66875?
CVE-2026-66875 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-66875?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66875, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-66875

Explore →

Is Your Infrastructure Affected by CVE-2026-66875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.