CVE-2026-0171

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
8.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: 8.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 out-of-bounds write due to a logic error in the code. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

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

Published

September 15, 2026

Last Modified

September 21, 2026

Advisory Details (1)

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

Pixel Update Bulletin—September 2026  |  Android Open Source Project

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

Vendor Advisories for CVE-2026-0171(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 21× in last 7d / 36× 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 07:59 UTCGHSA enrichment
  2. 2026-09-24 19:46 UTCEG score recompute
  3. 2026-09-24 19:46 UTCGHSA enrichment
  4. 2026-09-24 07:34 UTCGHSA enrichment
  5. 2026-09-23 19:20 UTCGHSA enrichment
  6. 2026-09-23 06:08 UTCGHSA enrichment
  7. 2026-09-22 17:55 UTCEG score recompute
  8. 2026-09-22 17:55 UTCGHSA enrichment
  9. 2026-09-22 05:42 UTCEG score recompute
  10. 2026-09-22 05:42 UTCGHSA enrichment
  11. 2026-09-21 17:29 UTCGHSA enrichment
  12. 2026-09-21 09:44 UTCGHSA enrichment
  13. 2026-09-20 21:32 UTCEG score recompute
  14. 2026-09-20 21:32 UTCGHSA enrichment
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-20 09:19 UTCGHSA enrichment
  17. 2026-09-19 21:06 UTCGHSA enrichment
  18. 2026-09-19 08:53 UTCGHSA enrichment
  19. 2026-09-18 20:40 UTCEG score recompute
  20. 2026-09-18 20:40 UTCGHSA enrichment
  21. 2026-09-18 19:27 UTCEPSS rescore
  22. 2026-09-18 08:15 UTCGHSA enrichment
  23. 2026-09-17 20:02 UTCEG score recompute
  24. 2026-09-17 20:02 UTCGHSA enrichment
  25. 2026-09-17 07:48 UTCGHSA enrichment
Show 11 more
  1. 2026-09-16 19:35 UTCGHSA enrichment
  2. 2026-09-16 17:54 UTCEG score recompute
  3. 2026-09-16 17:54 UTCGHSA enrichment
  4. 2026-09-16 04:26 UTCGHSA enrichment
  5. 2026-09-16 04:17 UTCEG score recompute
  6. 2026-09-16 04:16 UTCGHSA enrichment
  7. 2026-09-15 20:58 UTCEG score recompute▲ 8.80
  8. 2026-09-15 20:57 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  9. 2026-09-15 19:32 UTCNVD update
  10. 2026-09-15 18:40 UTCEG score recompute
  11. 2026-09-15 18:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-0171?

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

Book a Demo →Browse All CVEs