CVE-2026-0012

MEDIUMNVD 6.26.2
EchelonGraph scoreMEDIUM confidence

Score 6.2 from GitHub Security Advisory published 2026-03-02. NVD baseline CVSS 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: None knownExposed: 0

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

In setHideSensitive of ExpandableNotificationRow.java, there is a possible contact name leak due 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
6.2
EG Score
6.2(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity62% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

March 2, 2026

Last Modified

August 26, 2026

Advisory Details (1)

Auto-updated Aug 4, 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

Vendor Advisories for CVE-2026-0012(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-0012?
CVE-2026-0012 is a medium vulnerability published on March 2, 2026. In setHideSensitive of ExpandableNotificationRow.java, there is a possible contact name leak due 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-0012 disclosed?
CVE-2026-0012 was first published in the National Vulnerability Database on March 2, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0012 actively exploited?
CVE-2026-0012 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 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-0012?
CVE-2026-0012 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-0012?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0012, 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-0012

Explore →

Is Your Infrastructure Affected by CVE-2026-0012?

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