CVE-2026-44852
Arubanetworks Arubaos 6.5.4.0 – 8.10.0.22
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-44852 is a high-severity Improper Following of a Certificate's Chain of Trust (CWE-296) vulnerability in Arubanetworks Arubaos. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-17 (Public Key Infrastructure Certificates) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-29802
Vulnerability Data
An authenticated remote code execution vulnerability exists in the AOS-8 and AOS-10 web-based management interface. A vulnerability in the certificate download functionality could allow an authenticated remote attacker to overwrite arbitrary files on the underlying operating system by exploiting improper…
more
input validation in the file path parameter. Successful exploitation could allow the attacker to execute arbitrary commands on the underlying operating system as a privileged user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 12 hardening rules · 5 OS baselines
—
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
SC-17 requires proper issuance and management of PKI certificates, which structurally enforces correct chain-of-trust validation.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Proper service/hardware authentication requires correct certificate chain validation to a trusted root.
Pre-acquisition authenticity checks may surface certificate issues but do not address runtime chain-following logic.
Verifying identity assertions includes ensuring certificate chains are followed correctly.
Protecting data-in-transit commonly depends on TLS certificate chain validation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect missing or incorrect certificate chain validation.
A.8.24 mandates approved cryptographic practices and standards (guidance item f), which would include proper certificate chain validation as a required usage practice, so a system under a well-implemented policy is directed to follow the chain correctly; however, the weakness is an implementation defect in code, and the policy sets the standard without enforcing correct implementation, leaving third-party libraries and developer mistakes as a nameable remainder.
Secure coding standards address correct certificate chain validation.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
Oracle Linux 8 (1 rule)
- V-248531 OL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296
Oracle Linux 9 (1 rule)
- V-271604 OL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296
RHEL 8 (1 rule)
- V-230229 RHEL 8, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296
RHEL 9 (1 rule)
- V-258131 RHEL 9, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. blocks CWE-296