CVE-2026-0158

MEDIUMPre-NVD 4.04.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 4.0 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: <0.1% (below the 1st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 3.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-16) is not newer than that change (2026-10-25), so it does not.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2026-37192 (ENISA EUVD) · GHSA-hm6m-fqm4-j6w8 (GitHub Security Advisories)Source: ENISA EUVD

4.0EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • 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 Camera, there is a possible unauthorized way to access photos due to a missing permission check. 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 impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity40% × 45%
Impact severity (EG Severity): CVSS 4.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation<0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.0): severity, escalated by confirmed exploitation. This CVE's 4.0 is its impact severity (EG Severity), not escalated.

EG Severity
4.0 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 16, 2026

Last Modified

October 25, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
No fix on record yet.
Web page

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-0158(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 5× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 67 is merged into the row it repeats.

  1. 2026-10-27 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  2. 2026-10-26 16:30 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-10-25 23:37 UTCEG score recompute
  4. 2026-10-25 23:37 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  5. 2026-10-25 15:59 UTCEG score recompute
  6. 2026-10-23 10:28 UTCEG score recompute
  7. 2026-10-23 10:28 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  8. 2026-10-18 05:13 UTCEG score recompute
  9. 2026-10-17 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-10-15 16:31 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  11. 2026-10-12 16:42 UTCEG score recompute
  12. 2026-10-11 20:17 UTCEG score recompute
  13. 2026-10-11 18:30 UTCEG score recompute
  14. 2026-10-11 15:03 UTCEG score recompute
  15. 2026-10-10 19:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-08 17:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-07 23:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-06 15:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-09-23 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-09-16 17:53 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  23. 2026-09-16 17:13 UTCEG score recompute▲ 0.70
  24. 2026-09-16 17:13 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  25. 2026-09-16 16:19 UTCMITRE cvelistV5CVSS v3 → 4 · severity → MEDIUM
Show 41 more
  1. 2026-09-14 03:28 UTCEG score recompute
  2. 2026-09-14 03:28 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  3. 2026-09-04 05:06 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-09-01 04:39 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-08-30 22:43 UTCEG score recompute
  6. 2026-08-30 22:43 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  7. 2026-08-23 15:26 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  8. 2026-08-20 16:18 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  9. 2026-08-17 15:51 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  10. 2026-08-14 16:42 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  11. 2026-08-11 17:33 UTCEG score recompute
  12. 2026-08-11 17:33 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  13. 2026-08-11 13:42 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  14. 2026-08-08 18:24 UTCEG score recompute
  15. 2026-08-08 18:24 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  16. 2026-08-06 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-08-05 19:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-08-05 19:15 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  19. 2026-08-02 03:18 UTCEG score recompute
  20. 2026-08-02 03:18 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  21. 2026-07-30 04:09 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  22. 2026-07-26 19:46 UTCEG score recompute
  23. 2026-07-26 19:46 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  24. 2026-07-23 03:04 UTCEG score recompute
  25. 2026-07-16 22:37 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  26. 2026-07-13 19:17 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  27. 2026-07-10 20:09 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  28. 2026-07-08 15:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  29. 2026-07-07 20:59 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  30. 2026-07-07 13:46 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  31. 2026-07-04 18:30 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  32. 2026-07-01 16:58 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  33. 2026-06-28 17:50 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  34. 2026-06-25 18:37 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  35. 2026-06-22 19:28 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  36. 2026-06-19 20:17 UTCEG score recompute
  37. 2026-06-19 20:17 UTCGHSA enrichmentGHSA-hm6m-fqm4-j6w8 · GitHub severity LOW · GitHub CVSS 3.3
  38. 2026-06-17 19:50 UTCNVD updateCVSS v3 → 3.3 · severity → LOW
  39. 2026-06-17 17:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  40. 2026-06-16 21:07 UTCEG score recompute
  41. 2026-06-16 21:07 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-0158?
CVE-2026-0158 is a medium-severity vulnerability; its CVE record was published on June 16, 2026. In Camera, there is a possible unauthorized way to access photos due to a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
When was the CVE record for CVE-2026-0158 published?
The CVE record for CVE-2026-0158 was published on June 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-0158 actively exploited?
CVE-2026-0158 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-0158?
CVE-2026-0158 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-0158?
No fix for CVE-2026-0158 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-0158 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-0158?

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