CVE-2026-0054

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

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

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-09-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
3.3EG
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: 3.3Exploit: 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 isCallerAllowed of WalletContextualLocationsService.kt, there is a possible way to get wallet information 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
3.3
EG Score
3.3LOWmedium confidence
EG Risk
15
EG Risk 15/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 (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
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

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

September 8, 2026

Last Modified

September 15, 2026

References (1)

Vendor Advisories for CVE-2026-0054(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 / 24× 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.

  1. 2026-10-12 16:42 UTCEG score recompute
  2. 2026-10-11 20:17 UTCEG score recompute
  3. 2026-10-11 18:30 UTCEG score recompute
  4. 2026-10-11 15:03 UTCEG score recompute
  5. 2026-10-09 20:40 UTCEG score recompute
  6. 2026-10-09 20:40 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  7. 2026-10-08 17:11 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-10-06 10:22 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  11. 2026-10-03 10:46 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  12. 2026-09-30 08:50 UTCEG score recompute
  13. 2026-09-30 08:50 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  14. 2026-09-27 09:59 UTCEG score recompute
  15. 2026-09-27 09:59 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  16. 2026-09-24 11:09 UTCEG score recompute
  17. 2026-09-24 11:09 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  18. 2026-09-23 13:47 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-09-21 12:18 UTCEG score recompute
  20. 2026-09-21 12:18 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-09-18 13:27 UTCEG score recompute
  23. 2026-09-18 13:27 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  24. 2026-09-15 14:36 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  25. 2026-09-13 17:14 UTCEG score recompute
Show 12 more
  1. 2026-09-13 17:14 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf · GitHub severity LOW · GitHub CVSS 3.3
  2. 2026-09-12 15:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-09-11 14:52 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-09-10 18:23 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf
  6. 2026-09-10 17:25 UTCEG score recomputeFirst assessed: 3.3 LOW
  7. 2026-09-10 17:25 UTCGHSA enrichmentGHSA-rmgm-2rq2-74rf
  8. 2026-09-10 17:24 UTCMITRE cvelistV5CVSS v3 → 3.3 · severity → LOW
  9. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-09-08 19:30 UTCNVD update
  11. 2026-09-08 18:32 UTCEG score recompute
  12. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-0054?
CVE-2026-0054 is a low-severity vulnerability; its CVE record was published on September 8, 2026. In isCallerAllowed of WalletContextualLocationsService.kt, there is a possible way to get wallet information 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-0054 published?
The CVE record for CVE-2026-0054 was published on September 8, 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 September 15, 2026; the record at its source may have been updated since.
Is CVE-2026-0054 actively exploited?
CVE-2026-0054 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-0054?
CVE-2026-0054 has a CVSS v3.1 base score of 3.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-0054?
No fix for CVE-2026-0054 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-0054 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-0054?

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

Book a Demo →Browse All CVEs