# CVE-2026-66875: Mira Hormone Monitor, Mira Android App Missing authentication for critical function

> Remote attackers can rebind the device, steal hormone data, and cause denial of service due to missing authentication in the firmware and app.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-hqrj-p65x-4mf9

## What is CVE-2026-66875?

CVE-2026-66875 is a high-severity missing authorization vulnerability in Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-66875?


## How do I fix CVE-2026-66875?

No fix has been published for CVE-2026-66875 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-66875 being exploited?

There is no known exploitation of CVE-2026-66875 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-66875 and fix it if it is affected.

What it is: CVE-2026-66875 is a high-severity missing authorization vulnerability in Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App, published on 11 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66875 in the wild and no public exploit code.

Affected product: Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-66875/ (Markdown: https://insights.sbomify.com/CVE-2026-66875/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-66875
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-66875
- OSV: https://osv.dev/vulnerability/CVE-2026-66875

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-66875/
Summaries are generated and may contain mistakes; the official description above is the record.