CVE-2026-55266

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-05. 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 — 5 sources updated this week
7.8EG
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.8Exploit: None knownExposed services: Not assessed

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

In qsort of libufdt_sysdeps_vendor.c, there is a possible out-of-bounds write due to resource exhaustion. 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.8HIGHhigh confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0% × 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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
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).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

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
No fix on record yet.
generic

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-55266(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 32× in last 7d / 32× 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 18:00 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-11 16:54 UTCEG score recompute
  3. 2026-10-11 14:17 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-11 06:54 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-10 20:04 UTCEG score recompute
  7. 2026-10-10 20:04 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  9. 2026-10-10 09:14 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-09 22:21 UTCEG score recompute
  11. 2026-10-09 22:20 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  13. 2026-10-09 11:29 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-08 23:46 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-08 12:55 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-08 02:01 UTCEG score recompute
  17. 2026-10-08 02:01 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-10-07 15:11 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-07 12:32 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-07 01:42 UTCEG score recompute
  22. 2026-10-07 01:41 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  24. 2026-10-06 14:51 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-06 04:35 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
Show 7 more
  1. 2026-10-06 04:04 UTCEG score recompute
  2. 2026-10-06 04:04 UTCGHSA enrichmentGHSA-jg96-rqrj-v9p3 · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-05 20:12 UTCEG score recompute▲ 7.80
  4. 2026-10-05 20:10 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  5. 2026-10-05 19:24 UTCNVD update
  6. 2026-10-05 18:49 UTCEG score recompute
  7. 2026-10-05 18:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55266?
CVE-2026-55266 is a high-severity vulnerability; its CVE record was published on October 5, 2026. In qsort of libufdtsysdepsvendor.c, there is a possible out-of-bounds write due to resource exhaustion. 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-55266 published?
The CVE record for CVE-2026-55266 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-55266 actively exploited?
CVE-2026-55266 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-55266?
CVE-2026-55266 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-55266?
No fix for CVE-2026-55266 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-55266 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-55266?

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

Book a Demo →Browse All CVEs