CVE-2026-0038

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

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

In multiple functions of mem_protect.c, there is a possible way to execute arbitrary code due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

March 2, 2026

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

Android Security Bulletin—March 2026  |  Android Open Source Project

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

f090d4b083a9ef4831f99e692c239542dd385cb4 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/f090d4b083a9ef4831f99e692c239542dd385cb4
generic

d884f499434c224285c30d460681f1ce76a8cf1f - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/d884f499434c224285c30d460681f1ce76a8cf1f
generic

b23a5bfa1fb8f9525e21f095a87486a2bd856321 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/b23a5bfa1fb8f9525e21f095a87486a2bd856321
generic

7e1d15d29b7fe0f858926a8bcaf929b75db9e52a - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/7e1d15d29b7fe0f858926a8bcaf929b75db9e52a
generic

652b7b6bf9a62cc12c3a071bab4e92314f046739 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/652b7b6bf9a62cc12c3a071bab4e92314f046739
generic

513ea99ae008b81dd266bf6e361627c058ddde41 - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/513ea99ae008b81dd266bf6e361627c058ddde41
generic

1bf8033b56a45165602f8116e0a0d2e767f1e8ae - kernel/common - Git at Google

https://android.googlesource.com/kernel/common/+/1bf8033b56a45165602f8116e0a0d2e767f1e8ae

Vendor Advisories for CVE-2026-0038(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 21× 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-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 05:14 UTCEPSS rescore
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 09:34 UTCEPSS rescore
  8. 2026-09-08 22:00 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:21 UTCEPSS rescore
  17. 2026-08-28 21:40 UTCEPSS rescore
  18. 2026-08-27 14:24 UTCEPSS rescore
  19. 2026-08-25 13:48 UTCEPSS rescore
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:48 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-18 13:48 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 43 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 21:03 UTCGHSA enrichment
  4. 2026-08-14 08:44 UTCEG score recompute
  5. 2026-08-14 08:44 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 00:35 UTCEG score recompute
  8. 2026-08-13 00:35 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-11 23:25 UTCEG score recompute
  11. 2026-08-11 23:25 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 05:59 UTCEG score recompute
  14. 2026-08-11 05:59 UTCGHSA enrichment
  15. 2026-08-10 23:59 UTCEPSS rescore
  16. 2026-08-10 09:05 UTCGHSA enrichment
  17. 2026-08-09 20:41 UTCEG score recompute
  18. 2026-08-09 20:41 UTCGHSA enrichment
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 08:21 UTCEG score recompute
  21. 2026-08-09 08:21 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 08:38 UTCGHSA enrichment
  24. 2026-08-07 20:18 UTCEG score recompute
  25. 2026-08-07 20:18 UTCGHSA enrichment
  26. 2026-08-06 13:46 UTCEPSS rescore
  27. 2026-08-06 02:50 UTCEG score recompute
  28. 2026-08-06 02:50 UTCGHSA enrichment
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-04 15:09 UTCEPSS rescore
  31. 2026-08-04 10:38 UTCEPSS rescore
  32. 2026-08-04 04:36 UTCEG score recompute
  33. 2026-08-04 04:36 UTCGHSA enrichment
  34. 2026-08-03 10:35 UTCEPSS rescore
  35. 2026-08-02 19:11 UTCEG score recompute
  36. 2026-08-02 19:11 UTCGHSA enrichment
  37. 2026-08-02 02:26 UTCEPSS rescore
  38. 2026-08-01 04:15 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-28 15:36 UTCEPSS rescore
  41. 2026-07-27 14:13 UTCEPSS rescore
  42. 2026-07-27 12:54 UTCEG score recompute
  43. 2026-07-27 12:54 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-0038?
CVE-2026-0038 is a high vulnerability published on March 2, 2026. In multiple functions of mem_protect.c, there is a possible way to execute arbitrary code due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-0038 disclosed?
CVE-2026-0038 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0038 actively exploited?
CVE-2026-0038 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 85.5% of all scored CVEs.
What is the CVSS score of CVE-2026-0038?
CVE-2026-0038 has a CVSS v3.1 base score of 8.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0038?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0038, 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-0038

Explore →

Is Your Infrastructure Affected by CVE-2026-0038?

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

Start Free Scan →Browse All CVEs