CVE-2026-0134

MEDIUMPre-NVD 4.04.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.0 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss, ghsa
4.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 4.0Exploit: None knownExposed services: Not assessed

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

In PostWipeData of recovery_ui.cpp, there is a possible data persistence issue after a factory reset due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
4.0
EG Score
4.0MEDIUMmedium confidence
EG Risk
18
EG Risk 18/100

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
Severity40% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

Published

June 16, 2026

Last Modified

September 16, 2026

Advisory Details (1)

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0134?
CVE-2026-0134 is a medium vulnerability published on June 16, 2026. In PostWipeData of recovery_ui.cpp, there is a possible data persistence issue after a factory reset due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-0134 disclosed?
CVE-2026-0134 was first published on June 16, 2026, with the most recent update on September 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-0134 actively exploited?
CVE-2026-0134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0134?
CVE-2026-0134 has a CVSS v3.1 base score of 4.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0134?
No fix for CVE-2026-0134 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. The vendor advisories EchelonGraph has for CVE-2026-0134 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0134

Explore →

Is Your Infrastructure Affected by CVE-2026-0134?

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

Book a Demo →Browse All CVEs