CVE-2026-28590

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
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 improper encryption key validation due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

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 15, 2026

Advisory Details (1)

Auto-updated Sep 10, 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-28590(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 14× in last 7d / 33× 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-19 16:37 UTCGHSA enrichment
  2. 2026-09-19 04:26 UTCGHSA enrichment
  3. 2026-09-18 16:16 UTCGHSA enrichment
  4. 2026-09-18 04:06 UTCGHSA enrichment
  5. 2026-09-17 15:56 UTCGHSA enrichment
  6. 2026-09-17 03:45 UTCGHSA enrichment
  7. 2026-09-16 15:35 UTCGHSA enrichment
  8. 2026-09-16 03:12 UTCGHSA enrichment
  9. 2026-09-15 15:02 UTCGHSA enrichment
  10. 2026-09-15 06:30 UTCGHSA enrichment
  11. 2026-09-14 18:20 UTCGHSA enrichment
  12. 2026-09-14 05:36 UTCGHSA enrichment
  13. 2026-09-13 17:26 UTCGHSA enrichment
  14. 2026-09-13 05:15 UTCGHSA enrichment
  15. 2026-09-12 17:05 UTCGHSA enrichment
  16. 2026-09-12 04:55 UTCGHSA enrichment
  17. 2026-09-11 16:45 UTCEG score recompute
  18. 2026-09-11 16:45 UTCGHSA enrichment
  19. 2026-09-11 14:52 UTCEPSS rescore
  20. 2026-09-11 04:34 UTCEG score recompute
  21. 2026-09-11 04:34 UTCGHSA enrichment
  22. 2026-09-10 16:24 UTCGHSA enrichment
  23. 2026-09-10 15:20 UTCEG score recompute▲ 7.80
  24. 2026-09-10 15:20 UTCGHSA enrichment
  25. 2026-09-10 15:20 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
Show 8 more
  1. 2026-09-10 09:34 UTCEPSS rescore
  2. 2026-09-10 04:38 UTCGHSA enrichment
  3. 2026-09-10 04:33 UTCNVD update
  4. 2026-09-10 04:06 UTCGHSA enrichment
  5. 2026-09-10 04:00 UTCMITRE cvelistV5
  6. 2026-09-08 19:30 UTCNVD update
  7. 2026-09-08 18:32 UTCEG score recompute
  8. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28590?
CVE-2026-28590 is a high vulnerability published on September 8, 2026. In multiple locations, there is a possible improper encryption key validation due to a logic error in the code. 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-28590 disclosed?
CVE-2026-28590 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28590 actively exploited?
CVE-2026-28590 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 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-28590?
CVE-2026-28590 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-28590?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28590, 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-28590

Explore →

Is Your Infrastructure Affected by CVE-2026-28590?

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

Start Free Scan →Browse All CVEs