# CVE-2026-66340: Mira Hormone Monitor, Mira Android App Improper restriction of excessive authentication attempts

> Attackers can brute-force user accounts due to missing rate limiting and lockout mechanisms in the Mira Android app authentication endpoints.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-r6p2-jjcr-jm7c

## What is CVE-2026-66340?

CVE-2026-66340 is a medium-severity authentication bypass vulnerability in Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Mira cloud authentication endpoints do not enforce per-account rate limiting, per-IP throttling, or account lockout after repeated failed login attempts. An attacker can use brute-force methods to obtain gain access to user accounts.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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


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

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

## Is CVE-2026-66340 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66340 is a medium-severity authentication bypass vulnerability in Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66340 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-66340/ (Markdown: https://insights.sbomify.com/CVE-2026-66340/index.md)
```

## Sources

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

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