Extreme Networks ExtremeXOS up to 31.7.3/33.1.99/33.7.0 Authentication random values
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 2.61- |
Summary
A vulnerability marked as problematic has been reported in Extreme Networks ExtremeXOS up to 31.7.3/33.1.99/33.7.0. This vulnerability affects unknown code of the component Authentication. This manipulation causes random values. This vulnerability appears as CVE-2026-8169. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability has been found in Extreme Networks ExtremeXOS up to 31.7.3/33.1.99/33.7.0 and classified as problematic. Affected by this vulnerability is an unknown code of the component Authentication. The manipulation with an unknown input leads to a random values vulnerability. The CWE definition for the vulnerability is CWE-330. The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers. As an impact it is known to affect confidentiality. The summary by CVE is:
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.
The advisory is shared at extremenetworks.com. This vulnerability is known as CVE-2026-8169 since 05/08/2026. The exploitation appears to be difficult. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
Upgrading to version 31.7.4, 32.7.4.15, 33.1.100 or 33.7.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-46047). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 31.7.0
- 31.7.1
- 31.7.2
- 31.7.3
- 33.0
- 33.1
- 33.1.0
- 33.1.1
- 33.1.2
- 33.1.3
- 33.1.4
- 33.1.5
- 33.1.6
- 33.1.7
- 33.1.8
- 33.1.9
- 33.1.10
- 33.1.11
- 33.1.12
- 33.1.13
- 33.1.14
- 33.1.15
- 33.1.16
- 33.1.17
- 33.1.18
- 33.1.19
- 33.1.20
- 33.1.21
- 33.1.22
- 33.1.23
- 33.1.24
- 33.1.25
- 33.1.26
- 33.1.27
- 33.1.28
- 33.1.29
- 33.1.30
- 33.1.31
- 33.1.32
- 33.1.33
- 33.1.34
- 33.1.35
- 33.1.36
- 33.1.37
- 33.1.38
- 33.1.39
- 33.1.40
- 33.1.41
- 33.1.42
- 33.1.43
- 33.1.44
- 33.1.45
- 33.1.46
- 33.1.47
- 33.1.48
- 33.1.49
- 33.1.50
- 33.1.51
- 33.1.52
- 33.1.53
- 33.1.54
- 33.1.55
- 33.1.56
- 33.1.57
- 33.1.58
- 33.1.59
- 33.1.60
- 33.1.61
- 33.1.62
- 33.1.63
- 33.1.64
- 33.1.65
- 33.1.66
- 33.1.67
- 33.1.68
- 33.1.69
- 33.1.70
- 33.1.71
- 33.1.72
- 33.1.73
- 33.1.74
- 33.1.75
- 33.1.76
- 33.1.77
- 33.1.78
- 33.1.79
- 33.1.80
- 33.1.81
- 33.1.82
- 33.1.83
- 33.1.84
- 33.1.85
- 33.1.86
- 33.1.87
- 33.1.88
- 33.1.89
- 33.1.90
- 33.1.91
- 33.1.92
- 33.1.93
- 33.1.94
- 33.1.95
- 33.1.96
- 33.1.97
- 33.1.98
- 33.1.99
- 33.2
- 33.3
- 33.4
- 33.5
- 33.6
- 33.7.0
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Random valuesCWE: CWE-330 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Upgrade: ExtremeXOS 31.7.4/32.7.4.15/33.1.100/33.7.1
Timeline
05/08/2026 CVE reserved07/20/2026 Advisory disclosed
07/20/2026 VulDB entry created
07/20/2026 VulDB entry last update
Sources
Advisory: extremenetworks.comStatus: Confirmed
CVE: CVE-2026-8169 (🔒)
GCVE (CVE): GCVE-0-2026-8169
GCVE (VulDB): GCVE-100-380713
EUVD: 🔒
Entry
Created: 07/20/2026 20:18Updated: 07/20/2026 21:58
Changes: 07/20/2026 20:18 (53), 07/20/2026 21:58 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.