LiveActive security incident?Get immediate response
CVE Record

CVE-2026-68067: Mira Hormone Monitor, Mira Android App Weak Authentication

The login endpoint on the Mira cloud API accepts any format-valid string in the password field and returns a live active session token for the account matching the supplied email address. An attacker could use an email address to control cloud accounts and access hormone record information and account settings.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in Mira’s cloud login could let anyone who knows a customer’s email address access that customer’s account without the correct password. This may expose hormone records and account settings and could allow unauthorized account control. No user interaction or prior access is required.

Executive priority

Treat this as an immediate privacy and account-integrity issue. Assign ownership now, determine organizational or patient exposure, contact Mira for remediation status, and prepare targeted communications. Do not claim known compromise or active exploitation without additional evidence.

Technical view

The Mira cloud API login endpoint reportedly validates password format but not whether the password belongs to the supplied email account. It returns a live session token after a format-valid password string. CVSS 3.1 rates this 9.8 critical: network-accessible, low complexity, unauthenticated, and capable of high confidentiality, integrity, and availability impact.

Likely exposure

Exposure centers on Mira cloud accounts used with the listed Mira Android App 4.5.15.4 and firmware 1.7.1.47. The supplied product data also marks default status as unaffected, creating an unresolved scope inconsistency. Confirm affected status through CISA and Mira before making fleet-wide conclusions.

Exploitation context

The source bundle provides no evidence of active exploitation, and CVE-2026-68067 is not identified as a CISA KEV entry. Exploitation would nevertheless require only remote access and knowledge of an account email according to the description, making opportunistic abuse plausible but not confirmed.

Researcher notes

CWE-1390 indicates weak authentication. The decisive failure occurs at the cloud API rather than necessarily within device firmware or application code. Publicly supplied evidence does not name a patch, fixed version, mitigation, exploitation campaign, or confirmed affected population. The contradictory default-unaffected metadata warrants direct source verification.

Mitigation direction

  • Check current CISA and Mira guidance for confirmed remediation or service-side changes.
  • Identify users and devices associated with the listed app and firmware versions.
  • Revoke active sessions if Mira provides an approved account-management capability.
  • Notify potentially affected users without asserting compromise unless investigation supports it.
  • Avoid treating password changes alone as sufficient until authentication enforcement is confirmed.

Validation and detection

  • Inventory Mira Android App 4.5.15.4 and firmware 1.7.1.47 deployments.
  • Confirm affected-version status with CISA or Mira because the supplied status data is inconsistent.
  • Review available Mira account and session records for unexpected access or settings changes.
  • Verify authentication enforcement only through authorized, controlled testing that avoids accessing customer data.
  • Confirm existing sessions are invalidated after any vendor-directed remediation.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-1390: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-68067 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9icscert
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——icscert

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-68067Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Quanovate Tech Inc. (operating as Mira / Mira Care)Mira Firmware1.7.1.47unaffected
Quanovate Tech Inc. (operating as Mira / Mira Care)Mira Android App4.5.15.4unaffected
Weakness

CWE details

CWE-1390

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.