CVE-2026-55277

HIGHPre-NVD 8.08.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.0Exploit: None knownExposed: 0

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

In checkUiccListenConfigNeeded of RoutingManager.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

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

Published

September 8, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 8, 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-55277(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 22× in last 7d / 62× 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-25 00:06 UTCEG score recompute
  2. 2026-09-25 00:06 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 11:03 UTCGHSA enrichment
  5. 2026-09-23 22:11 UTCEG score recompute
  6. 2026-09-23 22:11 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-23 09:19 UTCGHSA enrichment
  9. 2026-09-22 20:27 UTCEG score recompute
  10. 2026-09-22 20:27 UTCGHSA enrichment
  11. 2026-09-22 07:35 UTCEG score recompute
  12. 2026-09-22 07:35 UTCGHSA enrichment
  13. 2026-09-21 18:43 UTCGHSA enrichment
  14. 2026-09-21 05:51 UTCGHSA enrichment
  15. 2026-09-20 16:59 UTCGHSA enrichment
  16. 2026-09-20 04:07 UTCEG score recompute
  17. 2026-09-20 04:07 UTCGHSA enrichment
  18. 2026-09-19 15:15 UTCGHSA enrichment
  19. 2026-09-19 02:22 UTCEG score recompute
  20. 2026-09-19 02:22 UTCGHSA enrichment
  21. 2026-09-18 19:28 UTCEPSS rescore
  22. 2026-09-18 13:30 UTCGHSA enrichment
  23. 2026-09-18 00:37 UTCEG score recompute
  24. 2026-09-18 00:37 UTCGHSA enrichment
  25. 2026-09-17 19:31 UTCEPSS rescore
Show 37 more
  1. 2026-09-17 11:45 UTCGHSA enrichment
  2. 2026-09-16 22:53 UTCEG score recompute
  3. 2026-09-16 22:53 UTCGHSA enrichment
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 10:01 UTCEG score recompute
  6. 2026-09-16 10:01 UTCGHSA enrichment
  7. 2026-09-16 05:15 UTCEPSS rescore
  8. 2026-09-15 21:08 UTCGHSA enrichment
  9. 2026-09-15 08:16 UTCEG score recompute
  10. 2026-09-15 08:16 UTCGHSA enrichment
  11. 2026-09-15 03:11 UTCEPSS rescore
  12. 2026-09-14 19:24 UTCGHSA enrichment
  13. 2026-09-14 06:28 UTCGHSA enrichment
  14. 2026-09-13 17:36 UTCEG score recompute
  15. 2026-09-13 17:36 UTCGHSA enrichment
  16. 2026-09-13 16:47 UTCEPSS rescore
  17. 2026-09-13 04:44 UTCGHSA enrichment
  18. 2026-09-12 15:52 UTCEG score recompute
  19. 2026-09-12 15:52 UTCGHSA enrichment
  20. 2026-09-12 03:00 UTCEG score recompute
  21. 2026-09-12 03:00 UTCGHSA enrichment
  22. 2026-09-11 14:53 UTCEPSS rescore
  23. 2026-09-11 14:07 UTCEG score recompute
  24. 2026-09-11 14:07 UTCGHSA enrichment
  25. 2026-09-11 01:15 UTCGHSA enrichment
  26. 2026-09-10 12:23 UTCEG score recompute
  27. 2026-09-10 12:23 UTCGHSA enrichment
  28. 2026-09-10 09:35 UTCEPSS rescore
  29. 2026-09-09 23:31 UTCGHSA enrichment
  30. 2026-09-09 10:39 UTCGHSA enrichment
  31. 2026-09-08 21:46 UTCEG score recompute
  32. 2026-09-08 21:46 UTCGHSA enrichment
  33. 2026-09-08 20:30 UTCEG score recompute▲ 8.00
  34. 2026-09-08 20:29 UTCMITRE cvelistV5CVSS v3 → 8 · severity → HIGH
  35. 2026-09-08 19:30 UTCNVD update
  36. 2026-09-08 18:31 UTCEG score recompute
  37. 2026-09-08 18:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55277?
CVE-2026-55277 is a high vulnerability published on September 8, 2026. In checkUiccListenConfigNeeded of RoutingManager.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.
When was CVE-2026-55277 disclosed?
CVE-2026-55277 was first published in the National Vulnerability Database on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55277 actively exploited?
CVE-2026-55277 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 95.1% of all scored CVEs.
What is the CVSS score of CVE-2026-55277?
CVE-2026-55277 has a CVSS v3.1 base score of 8.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-55277?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55277, 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-55277

Explore →

Is Your Infrastructure Affected by CVE-2026-55277?

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

Book a Demo →Browse All CVEs