HPE AOS-CX up to 10.18.0001 API Endpoint access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $5k-$25k | 1.93+ |
Summary
A vulnerability has been found in HPE AOS-CX up to 10.10.1180/10.13.1180/10.16.1051/10.17.1021/10.18.0001 and classified as very critical. This affects an unknown part of the component API Endpoint. The manipulation leads to access control. This vulnerability is listed as CVE-2026-73762. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability, which was classified as very critical, has been found in HPE AOS-CX up to 10.10.1180/10.13.1180/10.16.1051/10.17.1021/10.18.0001. This issue affects an unknown part of the component API Endpoint. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A vulnerability has been identified in the API endpoint of AOS-CX that could allow a remote actor to circumvent existing access controls. In some cases this could enable unauthorized access to management functionality that should be restricted by the configured access control policy.
It is possible to read the advisory at support.hpe.com. The identification of this vulnerability is CVE-2026-73762 since 08/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/01/2026). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.hpe.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.9VulDB Meta Temp Score: 7.9
VulDB Base Score: 9.1
VulDB Temp Score: 9.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.6
CNA Vector (hpe): 🔒
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: Access controlCWE: CWE-284 / CWE-266
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: 🔒
Timeline
08/13/2026 CVE reserved09/01/2026 Advisory disclosed
09/01/2026 VulDB entry created
09/01/2026 VulDB entry last update
Sources
Vendor: hpe.comAdvisory: support.hpe.com
Status: Not defined
CVE: CVE-2026-73762 (🔒)
GCVE (CVE): GCVE-0-2026-73762
GCVE (VulDB): GCVE-100-397883
Entry
Created: 09/01/2026 23:23Changes: 09/01/2026 23:23 (61)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.