CVE-2026-28627

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In btm_sec_encrypt_change of btm_sec.cc, there is a possible downgrade attack due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
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-28627(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 19× in last 7d / 31× 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-18 23:02 UTCEG score recompute
  2. 2026-09-18 23:01 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 19:27 UTCEPSS rescore
  5. 2026-09-17 20:39 UTCEG score recompute
  6. 2026-09-17 20:39 UTCGHSA enrichment
  7. 2026-09-17 19:30 UTCEPSS rescore
  8. 2026-09-16 18:16 UTCEG score recompute
  9. 2026-09-16 18:16 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 14:11 UTCGHSA enrichment
  13. 2026-09-15 03:17 UTCEG score recompute
  14. 2026-09-15 03:17 UTCGHSA enrichment
  15. 2026-09-14 00:54 UTCEG score recompute
  16. 2026-09-14 00:54 UTCGHSA enrichment
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-12 22:32 UTCEG score recompute
  19. 2026-09-12 22:32 UTCGHSA enrichment
  20. 2026-09-12 15:01 UTCEPSS rescore
  21. 2026-09-11 20:09 UTCEG score recompute
  22. 2026-09-11 20:09 UTCGHSA enrichment
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-10 17:21 UTCGHSA enrichment
  25. 2026-09-10 17:13 UTCEG score recompute▲ 4.30
Show 6 more
  1. 2026-09-10 17:12 UTCGHSA enrichment
  2. 2026-09-10 17:09 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 19:30 UTCNVD update
  5. 2026-09-08 18:32 UTCEG score recompute
  6. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-28627?
CVE-2026-28627 is a medium vulnerability published on September 8, 2026. In btmsecencryptchange of btmsec.cc, there is a possible downgrade attack due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-28627 disclosed?
CVE-2026-28627 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-28627 actively exploited?
CVE-2026-28627 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 88.5% of all scored CVEs.
What is the CVSS score of CVE-2026-28627?
CVE-2026-28627 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-28627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28627, 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-28627

Explore →

Is Your Infrastructure Affected by CVE-2026-28627?

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

Start Free Scan →Browse All CVEs