In dialInternal in multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2026-55270
HIGHPre-NVD 7.87.8—Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHhigh confidence
- EG Risk
- 35EG Risk 35/100CISA SSVC
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 computedSeverity78% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 5, 2026
Last Modified
October 7, 2026
Advisory Details (1)
Auto-updated Oct 5, 2026Fix referenced — no release confirmed yet.
generic
Android Security Bulletin—October 2026 | Android Open Source Project
https://source.android.com/docs/security/bulletin/2026/2026-10-01Vendor Advisories for CVE-2026-55270(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 15× in last 7d / 15× 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.
- 2026-10-07 23:48 UTCEPSS rescore
- 2026-10-07 15:32 UTCGHSA enrichment
- 2026-10-07 03:34 UTCEG score recompute
- 2026-10-07 03:34 UTCGHSA enrichment
- 2026-10-06 15:18 UTCEPSS rescore
- 2026-10-06 14:51 UTCGHSA enrichment
- 2026-10-06 04:35 UTCGHSA enrichment
- 2026-10-06 04:04 UTCEG score recompute
- 2026-10-06 04:04 UTCGHSA enrichment
- 2026-10-05 20:24 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
- 2026-10-05 19:24 UTCNVD update
- 2026-10-05 19:21 UTCEG score recompute▲ 7.80
- 2026-10-05 19:20 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
- 2026-10-05 18:49 UTCEG score recompute
- 2026-10-05 18:45 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55270?
CVE-2026-55270 is a high vulnerability published on October 5, 2026. In dialInternal in multiple locations, there is a possible permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-55270 disclosed?
CVE-2026-55270 was first published on October 5, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55270 actively exploited?
CVE-2026-55270 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-55270?
CVE-2026-55270 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-55270?
A fix for CVE-2026-55270 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-55270 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-55270
Is Your Infrastructure Affected by CVE-2026-55270?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.