CVE-2026-58880

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 5 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 7.0Exploit: 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).

In handle_app_val_response of btif_rc.cc, there is a possible way to achieve code execution due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
The EG Score, 7.0 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: 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

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). 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)14 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 total (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

October 5, 2026

Last Modified

October 7, 2026

Advisory Details (1)

Auto-updated Oct 5, 2026
Fix referenced — no release confirmed yet.
Web page

Android Security Bulletin—October 2026  |  Android Open Source Project

https://source.android.com/docs/security/bulletin/2026/2026-10-01

Vendor Advisories for CVE-2026-58880(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 28× in last 7d / 28× 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-11 19:36 UTCEG score recompute
  2. 2026-10-11 16:51 UTCEG score recompute
  3. 2026-10-11 14:14 UTCEG score recompute
  4. 2026-10-11 12:03 UTCEG score recompute
  5. 2026-10-11 12:03 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  6. 2026-10-10 22:48 UTCEG score recompute
  7. 2026-10-10 22:48 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-10 09:35 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  10. 2026-10-09 20:22 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  11. 2026-10-09 07:10 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  12. 2026-10-08 17:58 UTCEG score recompute
  13. 2026-10-08 17:57 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-08 04:45 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  16. 2026-10-07 15:32 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  17. 2026-10-07 04:03 UTCEG score recompute
  18. 2026-10-07 04:03 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-10-06 14:51 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  21. 2026-10-06 04:35 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  22. 2026-10-06 04:03 UTCEG score recompute
  23. 2026-10-06 04:03 UTCGHSA enrichmentGHSA-gq3m-h99r-pxxg · GitHub severity HIGH · GitHub CVSS 7.0
  24. 2026-10-05 19:31 UTCEG score recomputeFirst assessed: 7.0 HIGH
  25. 2026-10-05 19:30 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
Show 3 more
  1. 2026-10-05 19:24 UTCNVD update
  2. 2026-10-05 18:48 UTCEG score recompute
  3. 2026-10-05 18:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58880?
CVE-2026-58880 is a high-severity vulnerability; its CVE record was published on October 5, 2026. In handleappvalresponse of btifrc.cc, there is a possible way to achieve code execution due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
When was the CVE record for CVE-2026-58880 published?
The CVE record for CVE-2026-58880 was published on October 5, 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 7, 2026; the record at its source may have been updated since.
Is CVE-2026-58880 actively exploited?
CVE-2026-58880 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-58880?
CVE-2026-58880 has a CVSS v3.1 base score of 7.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-58880?
A fix for CVE-2026-58880 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-58880 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58880?

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

Book a Demo →Browse All CVEs