CVE-2026-0097

HIGHPre-NVD 8.08.0
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.0EG
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.0Exploit: None knownExposed: 0

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

In multiple locations, there is a possible way to bypass user interaction when pairing an LE device due to a logic error. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (1)

Auto-updated Jun 3, 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-0097(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 8× in last 7d / 29× 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.

Showing the most recent 100 of 222 total refreshes for this CVE.

  1. 2026-09-16 05:14 UTCEPSS rescore
  2. 2026-09-14 05:53 UTCEG score recompute
  3. 2026-09-14 05:53 UTCGHSA enrichment
  4. 2026-09-13 16:46 UTCEPSS rescore
  5. 2026-09-12 15:00 UTCEPSS rescore
  6. 2026-09-11 14:52 UTCEPSS rescore
  7. 2026-09-11 09:36 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 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 01:21 UTCEPSS rescore
  16. 2026-08-28 21:40 UTCEPSS rescore
  17. 2026-08-27 14:24 UTCEPSS rescore
  18. 2026-08-25 13:48 UTCEPSS rescore
  19. 2026-08-25 03:48 UTCEG score recompute
  20. 2026-08-25 03:48 UTCGHSA enrichment
  21. 2026-08-23 13:46 UTCGHSA enrichment
  22. 2026-08-21 14:48 UTCEG score recompute
  23. 2026-08-21 14:48 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:27 UTCGHSA enrichment
Show 75 more
  1. 2026-08-20 10:14 UTCEG score recompute
  2. 2026-08-20 10:14 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 04:33 UTCGHSA enrichment
  6. 2026-08-16 15:07 UTCEG score recompute
  7. 2026-08-16 15:07 UTCGHSA enrichment
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 03:10 UTCEG score recompute
  10. 2026-08-16 03:10 UTCGHSA enrichment
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 15:13 UTCEG score recompute
  13. 2026-08-15 15:13 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-14 23:12 UTCGHSA enrichment
  16. 2026-08-14 11:15 UTCGHSA enrichment
  17. 2026-08-13 23:18 UTCEG score recompute
  18. 2026-08-13 23:18 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 11:12 UTCGHSA enrichment
  21. 2026-08-12 23:12 UTCEG score recompute
  22. 2026-08-12 23:12 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-12 11:15 UTCGHSA enrichment
  25. 2026-08-11 23:02 UTCEG score recompute
  26. 2026-08-11 23:02 UTCGHSA enrichment
  27. 2026-08-11 13:42 UTCEPSS rescore
  28. 2026-08-11 11:05 UTCEG score recompute
  29. 2026-08-11 11:05 UTCGHSA enrichment
  30. 2026-08-10 23:59 UTCEPSS rescore
  31. 2026-08-10 23:08 UTCGHSA enrichment
  32. 2026-08-10 08:12 UTCGHSA enrichment
  33. 2026-08-09 20:16 UTCEG score recompute
  34. 2026-08-09 20:16 UTCGHSA enrichment
  35. 2026-08-09 13:46 UTCEPSS rescore
  36. 2026-08-09 08:19 UTCGHSA enrichment
  37. 2026-08-08 20:22 UTCEG score recompute
  38. 2026-08-08 20:22 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 08:22 UTCGHSA enrichment
  41. 2026-08-07 20:25 UTCEG score recompute
  42. 2026-08-07 20:25 UTCGHSA enrichment
  43. 2026-08-07 08:28 UTCGHSA enrichment
  44. 2026-08-06 20:31 UTCEG score recompute
  45. 2026-08-06 20:31 UTCGHSA enrichment
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-06 08:35 UTCGHSA enrichment
  48. 2026-08-05 20:38 UTCEG score recompute
  49. 2026-08-05 20:37 UTCGHSA enrichment
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-04 22:27 UTCEG score recompute
  52. 2026-08-04 22:27 UTCGHSA enrichment
  53. 2026-08-04 15:09 UTCEPSS rescore
  54. 2026-08-04 10:38 UTCEPSS rescore
  55. 2026-08-04 03:45 UTCGHSA enrichment
  56. 2026-08-03 15:48 UTCEG score recompute
  57. 2026-08-03 15:48 UTCGHSA enrichment
  58. 2026-08-03 10:35 UTCEPSS rescore
  59. 2026-08-03 01:21 UTCGHSA enrichment
  60. 2026-08-02 13:24 UTCEG score recompute
  61. 2026-08-02 13:24 UTCGHSA enrichment
  62. 2026-08-02 02:26 UTCEPSS rescore
  63. 2026-08-02 01:27 UTCGHSA enrichment
  64. 2026-08-01 13:30 UTCEG score recompute
  65. 2026-08-01 13:30 UTCGHSA enrichment
  66. 2026-08-01 04:15 UTCEPSS rescore
  67. 2026-07-31 18:41 UTCGHSA enrichment
  68. 2026-07-31 05:40 UTCEG score recompute
  69. 2026-07-31 05:40 UTCGHSA enrichment
  70. 2026-07-30 16:27 UTCEPSS rescore
  71. 2026-07-29 10:58 UTCEG score recompute
  72. 2026-07-29 10:58 UTCGHSA enrichment
  73. 2026-07-28 15:36 UTCEPSS rescore
  74. 2026-07-28 03:46 UTCGHSA enrichment
  75. 2026-07-27 11:39 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-0097?
CVE-2026-0097 is a high vulnerability published on June 1, 2026. In multiple locations, there is a possible way to bypass user interaction when pairing an LE device due to a logic error. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-0097 disclosed?
CVE-2026-0097 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-0097 actively exploited?
CVE-2026-0097 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 97.8% of all scored CVEs.
What is the CVSS score of CVE-2026-0097?
CVE-2026-0097 has a CVSS v3.1 base score of 8.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0097?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0097, 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-0097

Explore →

Is Your Infrastructure Affected by CVE-2026-0097?

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