CVE-2026-36213

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.8Exploit: Elevated riskExposed: 0

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

An issue in Microvirt MEmu Android Emulator 9.2.7.0 allows a local attacker to escalate privileges via the MemuService.exe component.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
51(Track*)
EG Risk 51/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
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 16, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GitHub - sec-zone/CVE-2026-36213: CVE-2026-36213 | Local Privilege Escalation in MEmu Android Emulator 9.2.7.0 via Insecure Service Binary Permissions | Patched in 9.3.2 · GitHub

https://github.com/sec-zone/CVE-2026-36213

Vendor Advisories for CVE-2026-36213(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 10× in last 7d / 86× 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.

Showing the most recent 100 of 214 total refreshes for this CVE.

  1. 2026-08-30 23:11 UTCEG score recompute
  2. 2026-08-30 23:11 UTCGHSA enrichment
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-24 23:41 UTCEG score recompute
  10. 2026-08-24 23:41 UTCGHSA enrichment
  11. 2026-08-23 21:59 UTCGHSA enrichment
  12. 2026-08-23 09:51 UTCEG score recompute
  13. 2026-08-23 09:51 UTCGHSA enrichment
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 22:42 UTCGHSA enrichment
  17. 2026-08-21 09:54 UTCEG score recompute
  18. 2026-08-21 09:54 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 20:51 UTCGHSA enrichment
  21. 2026-08-20 08:43 UTCEG score recompute
  22. 2026-08-20 08:43 UTCGHSA enrichment
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-19 13:32 UTCEG score recompute
  25. 2026-08-19 13:32 UTCGHSA enrichment
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-17 11:54 UTCGHSA enrichment
  4. 2026-08-16 23:47 UTCEG score recompute
  5. 2026-08-16 23:47 UTCGHSA enrichment
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 11:38 UTCEG score recompute
  8. 2026-08-16 11:38 UTCGHSA enrichment
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 23:31 UTCGHSA enrichment
  11. 2026-08-15 10:32 UTCEG score recompute
  12. 2026-08-15 10:32 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 22:24 UTCGHSA enrichment
  15. 2026-08-14 10:17 UTCGHSA enrichment
  16. 2026-08-13 22:09 UTCEG score recompute
  17. 2026-08-13 22:09 UTCGHSA enrichment
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-13 09:45 UTCGHSA enrichment
  20. 2026-08-12 21:37 UTCEG score recompute
  21. 2026-08-12 21:37 UTCGHSA enrichment
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 09:30 UTCGHSA enrichment
  24. 2026-08-11 21:22 UTCEG score recompute
  25. 2026-08-11 21:22 UTCGHSA enrichment
  26. 2026-08-11 09:14 UTCEG score recompute
  27. 2026-08-11 09:14 UTCGHSA enrichment
  28. 2026-08-11 00:00 UTCEPSS rescore
  29. 2026-08-10 21:07 UTCGHSA enrichment
  30. 2026-08-10 08:59 UTCGHSA enrichment
  31. 2026-08-09 20:51 UTCEG score recompute
  32. 2026-08-09 20:51 UTCGHSA enrichment
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 08:43 UTCGHSA enrichment
  35. 2026-08-08 20:36 UTCEG score recompute
  36. 2026-08-08 20:36 UTCGHSA enrichment
  37. 2026-08-08 16:37 UTCEPSS rescore
  38. 2026-08-08 08:28 UTCGHSA enrichment
  39. 2026-08-07 20:21 UTCEG score recompute
  40. 2026-08-07 20:21 UTCGHSA enrichment
  41. 2026-08-07 08:13 UTCGHSA enrichment
  42. 2026-08-06 20:05 UTCEG score recompute
  43. 2026-08-06 20:05 UTCGHSA enrichment
  44. 2026-08-06 13:46 UTCEPSS rescore
  45. 2026-08-06 07:57 UTCGHSA enrichment
  46. 2026-08-05 19:50 UTCGHSA enrichment
  47. 2026-08-04 15:44 UTCEG score recompute
  48. 2026-08-04 15:44 UTCGHSA enrichment
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:38 UTCEPSS rescore
  51. 2026-08-03 22:07 UTCEG score recompute
  52. 2026-08-03 22:07 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-03 09:59 UTCGHSA enrichment
  55. 2026-08-02 21:26 UTCGHSA enrichment
  56. 2026-08-02 09:18 UTCEG score recompute
  57. 2026-08-02 09:18 UTCGHSA enrichment
  58. 2026-08-02 02:27 UTCEPSS rescore
  59. 2026-08-01 21:10 UTCGHSA enrichment
  60. 2026-08-01 09:02 UTCEG score recompute
  61. 2026-08-01 09:02 UTCGHSA enrichment
  62. 2026-08-01 04:16 UTCEPSS rescore
  63. 2026-07-31 13:23 UTCGHSA enrichment
  64. 2026-07-31 00:00 UTCEG score recompute
  65. 2026-07-31 00:00 UTCGHSA enrichment
  66. 2026-07-30 16:28 UTCEPSS rescore
  67. 2026-07-30 05:17 UTCEG score recompute
  68. 2026-07-30 05:17 UTCGHSA enrichment
  69. 2026-07-30 01:30 UTCEPSS rescore
  70. 2026-07-29 16:15 UTCGHSA enrichment
  71. 2026-07-29 04:07 UTCEG score recompute
  72. 2026-07-29 04:06 UTCGHSA enrichment
  73. 2026-07-28 01:59 UTCEG score recompute
  74. 2026-07-28 01:59 UTCGHSA enrichment
  75. 2026-07-27 14:13 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 GitHub PoC) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52615
    First seen Jul 6, 2026

    MEmu Android Emulator 9.2.7.0 - Local Privilege Escalation

    Open source ↗
  • GitHub PoCsec-zone/CVE-2026-36213
    First seen Jun 11, 2026

    CVE-2026-36213 | Local Privilege Escalation in MEmu Android Emulator 9.2.7.0 via Insecure Service Binary Permissions | Patched in 9.3.2

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-36213?
CVE-2026-36213 is a high vulnerability published on June 15, 2026. An issue in Microvirt MEmu Android Emulator 9.2.7.0 allows a local attacker to escalate privileges via the MemuService.exe component.
When was CVE-2026-36213 disclosed?
CVE-2026-36213 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-36213 actively exploited?
CVE-2026-36213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.4% of all scored CVEs.
What is the CVSS score of CVE-2026-36213?
CVE-2026-36213 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-36213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-36213, 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-36213

Explore →

Is Your Infrastructure Affected by CVE-2026-36213?

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

Start Free Scan →Browse All CVEs