CVE-2026-64934

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-08-12. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Mira Hormone Monitor, Mira Android App | CISA

Mira Hormone Monitor, Mira Android App | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/news-events/ics-medical-advisories/icsma-26-223-01

Vendor Advisories for CVE-2026-64934(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 31× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 18:16 UTCGHSA enrichment
  3. 2026-08-19 20:32 UTCEG score recompute
  4. 2026-08-19 20:32 UTCGHSA enrichment
  5. 2026-08-19 17:04 UTCEPSS rescore
  6. 2026-08-18 22:47 UTCEG score recompute
  7. 2026-08-18 22:47 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 00:52 UTCEG score recompute
  10. 2026-08-18 00:52 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 03:04 UTCEG score recompute
  13. 2026-08-17 03:04 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 05:20 UTCEG score recompute
  16. 2026-08-16 05:20 UTCGHSA enrichment
  17. 2026-08-15 07:36 UTCEG score recompute
  18. 2026-08-15 07:36 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 09:51 UTCEG score recompute
  21. 2026-08-14 09:51 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 12:07 UTCGHSA enrichment
  24. 2026-08-12 14:23 UTCEG score recompute
  25. 2026-08-12 14:23 UTCGHSA enrichment
Show 6 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-12 13:25 UTCEG score recompute
  3. 2026-08-12 13:25 UTCGHSA enrichment
  4. 2026-08-11 22:20 UTCEG score recompute
  5. 2026-08-11 21:25 UTCEG score recompute
  6. 2026-08-11 21:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64934?
CVE-2026-64934 is a medium vulnerability published on August 11, 2026. 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…
When was CVE-2026-64934 disclosed?
CVE-2026-64934 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64934 actively exploited?
CVE-2026-64934 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.8% of all scored CVEs.
What is the CVSS score of CVE-2026-64934?
CVE-2026-64934 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-64934?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64934, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64934

Explore →

Is Your Infrastructure Affected by CVE-2026-64934?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs