Skip to content
IoT

CVE-2026-67558

8.2
High
EPSS 0.18%Aug 12, 2026

BLE name substring auth allows token theft and forged hormone measurement injection.

common questions

Is CVE-2026-67558 being exploited?

Not confirmed. CVE-2026-67558 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.

How severe is CVE-2026-67558?

CVE-2026-67558 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-67558?

Not known from our data. No patch reference has been recorded for CVE-2026-67558, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-67558 affect?

CVE-2026-67558 affects Mira Android companion app v4.5.15.4, Mira hormone analyzer (BLE), Mira cloud service/clinical trend records. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67558?

Unpair device and disable BLE, restrict use, monitor records; apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Mira Android companion app v4.5.15.4Mira hormone analyzer (BLE)Mira cloud service/clinical trend records
impact

Spoof BLE name to capture session tokens and upload forged hormone readings to victim's cloud, altering clinical trends.

action required

Immediate action required

affected versions
Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App
  • affected4.5.15.4
Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Firmware
  • affected1.7.1.47

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free