CVE-2026-0100

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-02. 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
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

In Load of LoadedArsc.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.1%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

Android Security Bulletin—June 2026  |  Android Open Source Project

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0100?
CVE-2026-0100 is a high vulnerability published on June 1, 2026. In Load of LoadedArsc.cpp, there is a possible out of bounds write due to a heap buffer overflow. 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-0100 disclosed?
CVE-2026-0100 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0100 actively exploited?
CVE-2026-0100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-0100?
CVE-2026-0100 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-0100?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0100, 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-0100

Explore →

Is Your Infrastructure Affected by CVE-2026-0100?

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

Start Free Scan →Browse All CVEs