{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64934 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-64934 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-64934 is a medium-severity vulnerability in Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64934 and fix it if it is affected.\n\nWhat it is: CVE-2026-64934 is a medium-severity vulnerability in Quanovate Tech Inc. (operating as Mira / Mira Care) Mira Android App, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64934 in the wild and no public exploit code.\n\nAffected 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.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-64934/ (Markdown: https://insights.sbomify.com/CVE-2026-64934/index.md)","id":"CVE-2026-64934","markdown":"https://insights.sbomify.com/CVE-2026-64934/index.md","name":"CVE-2026-64934","record":{"aliases":["GHSA-v72c-jrwc-x8qx"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mira Android App","requires_auth":"low_privilege","summary":"An authenticated attacker can spoof firmware versions to bypass security update prompts and evade vendor vulnerability tracking in the Mira Android app.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-807","name":"Reliance on Untrusted Inputs in a Security Decision"}],"description":"The Mira cloud API accepts the firmware version reported by the companion app as authoritative for a given device, without independently attesting the version from the device itself. An authenticated attacker could submit arbitrary firmware version strings for their own device, allowing them to evade vendor-side vulnerable-fleet analytics, suppress security update prompts to the user, and misrepresent patch-adoption metrics.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Mira Hormone Monitor, Mira Android App Reliance on untrusted inputs in a security decision","id":"CVE-2026-64934","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in Tegalog -Fumy Otegaru Memo Logger-","id":"CVE-2026-64940"},"packages":[],"prev":{"headline":"Missing authorization in Red Hat Advanced Cluster Management for Kubernetes 2.11","id":"CVE-2026-64927"},"products":["Mira Android App","Mira Firmware"],"published":"2026-08-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["Quanovate Tech Inc. (operating as Mira / Mira Care)"]},"summary":"An authenticated attacker can spoof firmware versions to bypass security update prompts and evade vendor vulnerability tracking in the Mira Android app.","url":"https://insights.sbomify.com/CVE-2026-64934/"}