CVE-2020-0069

CRITICALNVD 7.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 1.4%CVSS: 7.8Exploit: cisa kev · ssvc active · public exploitExposed services: Not assessed

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

In the ioctl handlers of the Mediatek Command Queue driver, there is a possible out of bounds write due to insufficient input sanitization and missing SELinux restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-147882143References: M-ALPS04356754

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

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
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact, and watch the vendor's advisory for the fix.
EPSS PROB
1.4%
EPSS %ILE
70th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact, and watch the vendor's advisory for the fix.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 10, 2020

Last Modified

October 23, 2025

Advisory Details (3)

Auto-updated Jun 4, 2026
⚠️ Active exploitation confirmed. No fix on record yet. Sources: cisa.
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-0069
generic

Android Security Bulletin—March 2020  |  Android Open Source Project

https://source.android.com/security/bulletin/2020-03-01
generic

Security Advisory - Privilege Escalation Vulnerability in Some Huawei Products

http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200527-01-mtk-en

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 56× in last 7d / 260× 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 1,091 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

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

  • GitHub PoC0xf15h/mtk_su
    First seen Sep 4, 2023

    CVE-2020-0069

    Open source ↗
  • GitHub PoCquarkslab/CVE-2020-0069_poc
    First seen Mar 24, 2020
    Open source ↗
  • GitHub PoCTheRealJunior/mtk-su-reverse-cve-2020-0069
    First seen Mar 3, 2020

    reversing mtk-su

    Open source ↗
  • GitHub PoCR0rt1z2/AutomatedRoot
    First seen Sep 6, 2019

    Root your MediaTek device with CVE-2020-0069

    Open source ↗

Frequently asked(6)

What is CVE-2020-0069?
CVE-2020-0069 is a critical vulnerability published on March 10, 2020. In the ioctl handlers of the Mediatek Command Queue driver, there is a possible out of bounds write due to insufficient input sanitization and missing SELinux restrictions. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not…
When was CVE-2020-0069 disclosed?
CVE-2020-0069 was first published on March 10, 2020, with the most recent update on October 23, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-0069 actively exploited?
Yes. CISA added CVE-2020-0069 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting MediaTek Multiple Chipsets. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation, and watch the vendor's advisory for the fix.
What is the CVSS score of CVE-2020-0069?
CVE-2020-0069 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2020-0069?
CVE-2020-0069 affects MediaTek Multiple Chipsets.
How do I remediate CVE-2020-0069?
No fix for CVE-2020-0069 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-0069

Explore →

Is Your Infrastructure Affected by CVE-2020-0069?

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