Skip to main content
VulnerabilityPublished

CVE-2026-66832: Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Firmware · Use of GET request method with sensitive query strings

Affects Quanovate Tech Inc. (operating as Mira / Mira Care) Mira FirmwareSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium.

Data as of 9 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Quanovate Tech Inc. (operating as Mira / Mira Care)Mira FirmwareAffected
  • =1.7.1.47
Fixed in–
Quanovate Tech Inc. (operating as Mira / Mira Care)Mira Android AppAffected
  • =4.5.15.4
Fixed in–

AI-suggested

Until an official fix is available, users and administrators should avoid using version 1.7.1.47 of Mira Firmware where possible. Consider limiting or monitoring WebView usage that loads third-party content to reduce exposure of sensitive tokens.

Description

When the Mira Android app opens in-app WebView content (e.g., shop redirect flows), the user's live session token is appended to the URL as a query string parameter, and a persistent user identifier is included in the WebView's User-Agent header. Both are then transmitted to third-party web properties, referrer logs, and any JavaScript running in the WebView context.

References

Community reviews

Loading reviews…