AOS-CX: Cross-Site Request Forgery
CVE-2026-73780 is a high-severity cross-site request forgery vulnerability in AOS-CX from Hewlett Packard Enterprise, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected AOS-CX versions: 10.18.0000 through 10.18.0001; 10.17.0000 through 10.17.1021; 10.16.0000 through 10.16.1051, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.2% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Arubaos-cx to 10.10.1181 or 10.13.1190 or 10.16.1060 or 10.17.1030, whichever matches your release line, or a later version.
- Read the advisory on support.hpe.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Hewlett Packard Enterprise | AOS-CX | 10.18.0000 through 10.18.0001; 10.17.0000 through 10.17.1021; 10.16.0000 through 10.16.1051; 10.13.0000 through 10.13.1180; 10.10.0000 through 10.10.1180 | Not stated |
| Hewlett Packard Enterprise | Arubaos-cx | before 10.10.1181; 10.13.0000 up to, but not including, 10.13.1190; 10.16.0000 up to, but not including, 10.16.1060; 10.17.0000 up to, but not including, 10.17.1030; 10.18.0001 | 10.10.1181, 10.13.1190, 10.16.1060, 10.17.1030 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.3 | High | CNA (hpe.com) |
| CVSS 3.1 | 8.3 | High | NVD |
Official description
A vulnerability in the web-based management interface of AOS-CX switches exposes some sessions to a lack of Cross-Site Request Forgery (CSRF) protection. This could allow a remote unauthenticated attacker to execute arbitrary input against the affected interface if the attacker can convince an authenticated user of the interface to interact with a specially crafted URL.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Cross-Site Request Forgery
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, use anti-CSRF packages such as the OWASP CSRFGuard. Another example is the ESAPI Session Management control, which includes a component for CSRF.
- Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in AOS-CX
- 8.8 High severity
- 8.4 High severity
- 8.2 High severity
- 9.8 Critical severity
- 8.1 High severity
- 7.9 High severity
Recent Cross-Site Request Forgery vulnerabilities
- 7.4 High severity
- 7.1 High severity
- 8.1 High severity
- 7.5 High severity
- 8.4 High severity
- 8.8 High severity
Spotted an error? Tell us.