# CVE-2026-67558: Mira Hormone Monitor, Mira Android App Authentication bypass by spoofing

> Attackers can spoof Bluetooth devices to bypass authentication, allowing them to inject forged hormone data and steal session tokens from the Mira Android app.

- **Severity:** High 8.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-cxxh-6vq9-57gc

## What is CVE-2026-67558?

CVE-2026-67558 is a high-severity authentication bypass 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, and only if a user opens a file or follows a link.

### Official description

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 information and inject forged hormone measurements into the victim's cloud record and clinical trend view.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-67558 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67558 is a high-severity authentication bypass 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-67558 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-67558/ (Markdown: https://insights.sbomify.com/CVE-2026-67558/index.md)
```

## Sources

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

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