CVE-2026-0133

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

In smmu_attach_dev of arm-smmu-v3.c, there is a possible way to sign malicious Android Runtime bootclass artifacts due to a missing permission check. 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
40(Track)
EG Risk 40/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 17, 2026

Advisory Details (1)

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

Pixel Update Bulletin—June 2026  |  Android Open Source Project

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

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

Frequently asked(5)

What is CVE-2026-0133?
CVE-2026-0133 is a high vulnerability published on June 16, 2026. In smmuattachdev of arm-smmu-v3.c, there is a possible way to sign malicious Android Runtime bootclass artifacts due to a missing permission check. 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-0133 disclosed?
CVE-2026-0133 was first published in the National Vulnerability Database on June 16, 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-0133 actively exploited?
CVE-2026-0133 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 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-0133?
CVE-2026-0133 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-0133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0133, 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-0133

Explore →

Is Your Infrastructure Affected by CVE-2026-0133?

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

Start Free Scan →Browse All CVEs