CVE-2016-8526 in the critical feed json
Aruba Airwave all versions up to, but not including, 8.2.3.1 is vulnerable to an XML external entities (XXE).
published 2018-08-06 8 y ago modified 2026-06-17 4 mo ago also EUVD-2016-9374
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.1%
- EPSS 10.1% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
Aruba Airwave all versions up to, but not including, 8.2.3.1 is vulnerable to an XML external entities (XXE). XXEs are a way to permit XML parsers to access storage that exist on external systems. If an unprivileged user is permitted to control the contents of XML files, XXE can be used as an attack vector. Because the XML parser has access to the local filesystem and runs with the permissions of the web server, it can access any file that is readable by the web server and copy it to an external system of the attacker's choosing. This could include files that contain passwords, which could then lead to privilege escalation.
Patch / fix
- hp airwave 8.2.3.1
Timeline
- First public exploit (EDB-41482)
- Published
Exploit prediction
10.13% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-41482 Aruba AirWave 8.2.3 - XML External Entity Injection / Cross-Site Scripting webapps, 2017-03-01
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- Hewlett Packard Enterprise Aruba AirWave
Classification
- Weakness
-
- CWE-611 Improper Restriction of XML External Entity Reference
References
-
exploit-db.com
/exploits/41482/
exploit, third-party-advisory, vdb-entry
-
arubanetworks.com
/assets/alert/ARUBA-PSA-2017-001.txt
vendor-advisory
-
securityfocus.com
/bid/96495
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-8526
- NVD CVE-2016-8526
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.