CVE-2026-8169

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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: epss, secondary
Trending — 4 sources updated this week
8.7
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.7Exploit: NoneExposed: 0

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

ExtremeXOS (EXOS) uses a challenge-response mechanism to authorize access to the privileged debug-mode function. The challenge value is generated using an insufficiently random source, which under certain conditions may allow an attacker to predict the expected response and activate debug-mode without authorization. Depending on device configuration and version, this may enable escalation to root-level access and persistent modification of the device software stack. Exploitation requires either a valid low-privilege account on the device (remote scenario) or physical serial console access (local scenario). This vulnerability is distinct from CVE-2017-14329, which addressed a different issue involving Python script privileges.

Extreme would like to thank Hadrien Barral (Université Gustave Eiffel) and Georges-Axel Jaloyan (French Ministry of the Interior) for responsible disclosure of their findings.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
20.0%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 21, 2026

References (1)

Vendor Advisories for CVE-2026-8169(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 170× in last 7d / 170× 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.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-07-23 03:23 UTCEG score recompute
  2. 2026-07-22 23:34 UTCEG score recompute
  3. 2026-07-22 23:34 UTCGHSA enrichment
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-20 20:43 UTCEG score recompute
  8. 2026-07-20 20:43 UTCGHSA enrichment
  9. 2026-07-20 20:36 UTCGHSA enrichment
  10. 2026-07-20 20:35 UTCGHSA enrichment
  11. 2026-07-20 20:35 UTCGHSA enrichment
  12. 2026-07-20 20:34 UTCGHSA enrichment
  13. 2026-07-20 20:32 UTCGHSA enrichment
  14. 2026-07-20 20:29 UTCGHSA enrichment
  15. 2026-07-20 20:28 UTCGHSA enrichment
  16. 2026-07-20 20:27 UTCGHSA enrichment
  17. 2026-07-20 20:25 UTCGHSA enrichment
  18. 2026-07-20 20:22 UTCGHSA enrichment
  19. 2026-07-20 20:22 UTCGHSA enrichment
  20. 2026-07-20 20:20 UTCGHSA enrichment
  21. 2026-07-20 20:19 UTCGHSA enrichment
  22. 2026-07-20 20:18 UTCGHSA enrichment
  23. 2026-07-20 20:17 UTCGHSA enrichment
  24. 2026-07-20 20:17 UTCGHSA enrichment
  25. 2026-07-20 20:17 UTCGHSA enrichment
Show 75 more
  1. 2026-07-20 20:14 UTCGHSA enrichment
  2. 2026-07-20 20:13 UTCGHSA enrichment
  3. 2026-07-20 20:11 UTCGHSA enrichment
  4. 2026-07-20 20:10 UTCGHSA enrichment
  5. 2026-07-20 20:10 UTCGHSA enrichment
  6. 2026-07-20 20:09 UTCGHSA enrichment
  7. 2026-07-20 20:09 UTCGHSA enrichment
  8. 2026-07-20 20:08 UTCGHSA enrichment
  9. 2026-07-20 20:07 UTCGHSA enrichment
  10. 2026-07-20 20:07 UTCGHSA enrichment
  11. 2026-07-20 20:06 UTCGHSA enrichment
  12. 2026-07-20 20:06 UTCGHSA enrichment
  13. 2026-07-20 20:05 UTCGHSA enrichment
  14. 2026-07-20 20:05 UTCGHSA enrichment
  15. 2026-07-20 20:04 UTCGHSA enrichment
  16. 2026-07-20 20:03 UTCGHSA enrichment
  17. 2026-07-20 20:01 UTCGHSA enrichment
  18. 2026-07-20 20:01 UTCGHSA enrichment
  19. 2026-07-20 20:00 UTCGHSA enrichment
  20. 2026-07-20 20:00 UTCGHSA enrichment
  21. 2026-07-20 19:59 UTCGHSA enrichment
  22. 2026-07-20 19:59 UTCGHSA enrichment
  23. 2026-07-20 19:58 UTCGHSA enrichment
  24. 2026-07-20 19:58 UTCGHSA enrichment
  25. 2026-07-20 19:57 UTCGHSA enrichment
  26. 2026-07-20 19:56 UTCGHSA enrichment
  27. 2026-07-20 19:56 UTCGHSA enrichment
  28. 2026-07-20 19:55 UTCGHSA enrichment
  29. 2026-07-20 19:54 UTCGHSA enrichment
  30. 2026-07-20 19:54 UTCGHSA enrichment
  31. 2026-07-20 19:52 UTCGHSA enrichment
  32. 2026-07-20 19:52 UTCGHSA enrichment
  33. 2026-07-20 19:51 UTCGHSA enrichment
  34. 2026-07-20 19:51 UTCGHSA enrichment
  35. 2026-07-20 19:50 UTCGHSA enrichment
  36. 2026-07-20 19:50 UTCGHSA enrichment
  37. 2026-07-20 19:49 UTCGHSA enrichment
  38. 2026-07-20 19:49 UTCGHSA enrichment
  39. 2026-07-20 19:48 UTCGHSA enrichment
  40. 2026-07-20 19:48 UTCGHSA enrichment
  41. 2026-07-20 19:47 UTCGHSA enrichment
  42. 2026-07-20 19:47 UTCGHSA enrichment
  43. 2026-07-20 19:46 UTCGHSA enrichment
  44. 2026-07-20 19:44 UTCGHSA enrichment
  45. 2026-07-20 19:43 UTCGHSA enrichment
  46. 2026-07-20 19:43 UTCGHSA enrichment
  47. 2026-07-20 19:42 UTCGHSA enrichment
  48. 2026-07-20 19:42 UTCGHSA enrichment
  49. 2026-07-20 19:41 UTCGHSA enrichment
  50. 2026-07-20 19:41 UTCGHSA enrichment
  51. 2026-07-20 19:40 UTCGHSA enrichment
  52. 2026-07-20 19:40 UTCGHSA enrichment
  53. 2026-07-20 19:39 UTCGHSA enrichment
  54. 2026-07-20 19:39 UTCGHSA enrichment
  55. 2026-07-20 19:38 UTCGHSA enrichment
  56. 2026-07-20 19:38 UTCGHSA enrichment
  57. 2026-07-20 19:37 UTCGHSA enrichment
  58. 2026-07-20 19:37 UTCGHSA enrichment
  59. 2026-07-20 19:36 UTCGHSA enrichment
  60. 2026-07-20 19:35 UTCGHSA enrichment
  61. 2026-07-20 19:34 UTCGHSA enrichment
  62. 2026-07-20 19:34 UTCGHSA enrichment
  63. 2026-07-20 19:33 UTCGHSA enrichment
  64. 2026-07-20 19:33 UTCGHSA enrichment
  65. 2026-07-20 19:32 UTCGHSA enrichment
  66. 2026-07-20 19:32 UTCGHSA enrichment
  67. 2026-07-20 19:32 UTCGHSA enrichment
  68. 2026-07-20 19:30 UTCGHSA enrichment
  69. 2026-07-20 19:29 UTCGHSA enrichment
  70. 2026-07-20 19:29 UTCGHSA enrichment
  71. 2026-07-20 19:28 UTCGHSA enrichment
  72. 2026-07-20 19:28 UTCGHSA enrichment
  73. 2026-07-20 19:28 UTCGHSA enrichment
  74. 2026-07-20 19:26 UTCGHSA enrichment
  75. 2026-07-20 19:26 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-8169?
CVE-2026-8169 is a high vulnerability published on July 20, 2026. ExtremeXOS (EXOS) uses a challenge-response mechanism to authorize access to the privileged debug-mode function. The challenge value is generated using an insufficiently random source, which under certain conditions may allow an attacker to predict the expected response and activate debug-mode…
When was CVE-2026-8169 disclosed?
CVE-2026-8169 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 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-8169 actively exploited?
CVE-2026-8169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8169?
CVE-2026-8169 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-8169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8169, 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-8169

Explore →

Is Your Infrastructure Affected by CVE-2026-8169?

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