CVE-2026-58820

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. 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
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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 memory safety issue due to integer overflow. This could lead to local escalation of privilege with no additional execution privileges required.

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

Published

September 8, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Sep 9, 2026
No patch confirmed yet.
generic

Android Security Bulletin—September 2026  |  Android Open Source Project

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

Vendor Advisories for CVE-2026-58820(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 20× in last 7d / 41× 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.

  1. 2026-09-21 05:04 UTCGHSA enrichment
  2. 2026-09-20 15:52 UTCGHSA enrichment
  3. 2026-09-20 03:12 UTCGHSA enrichment
  4. 2026-09-19 14:36 UTCGHSA enrichment
  5. 2026-09-19 02:00 UTCEG score recompute
  6. 2026-09-19 02:00 UTCGHSA enrichment
  7. 2026-09-18 19:28 UTCEPSS rescore
  8. 2026-09-18 13:24 UTCGHSA enrichment
  9. 2026-09-18 00:48 UTCEG score recompute
  10. 2026-09-18 00:48 UTCGHSA enrichment
  11. 2026-09-17 19:31 UTCEPSS rescore
  12. 2026-09-17 12:12 UTCGHSA enrichment
  13. 2026-09-16 23:35 UTCEG score recompute
  14. 2026-09-16 23:35 UTCGHSA enrichment
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 10:59 UTCGHSA enrichment
  17. 2026-09-15 22:23 UTCGHSA enrichment
  18. 2026-09-15 09:46 UTCGHSA enrichment
  19. 2026-09-14 21:10 UTCGHSA enrichment
  20. 2026-09-14 08:21 UTCGHSA enrichment
  21. 2026-09-13 19:46 UTCGHSA enrichment
  22. 2026-09-13 07:10 UTCGHSA enrichment
  23. 2026-09-12 18:35 UTCEG score recompute
  24. 2026-09-12 18:35 UTCGHSA enrichment
  25. 2026-09-12 05:59 UTCGHSA enrichment
Show 16 more
  1. 2026-09-11 17:24 UTCEG score recompute
  2. 2026-09-11 17:24 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 04:18 UTCGHSA enrichment
  5. 2026-09-10 15:42 UTCEG score recompute
  6. 2026-09-10 15:42 UTCGHSA enrichment
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-10 03:07 UTCEG score recompute
  9. 2026-09-10 03:07 UTCGHSA enrichment
  10. 2026-09-09 14:30 UTCGHSA enrichment
  11. 2026-09-09 13:27 UTCEG score recompute▲ 7.80
  12. 2026-09-09 13:27 UTCGHSA enrichment
  13. 2026-09-09 13:25 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  14. 2026-09-08 19:30 UTCNVD update
  15. 2026-09-08 18:31 UTCEG score recompute
  16. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58820?
CVE-2026-58820 is a high vulnerability published on September 8, 2026. In multiple locations, there is a possible memory safety issue due to integer overflow. This could lead to local escalation of privilege with no additional execution privileges required.
When was CVE-2026-58820 disclosed?
CVE-2026-58820 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58820 actively exploited?
CVE-2026-58820 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 99.8% of all scored CVEs.
What is the CVSS score of CVE-2026-58820?
CVE-2026-58820 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-58820?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58820, 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-58820

Explore →

Is Your Infrastructure Affected by CVE-2026-58820?

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

Start Free Scan →Browse All CVEs